Electra Protocol multi-layer explorer

✓All services are running properly
Supply: 18,459,303,672 XEPContracts: 322Block height: 2,205,128Connected nodes: 275
Certelo by Evoblox
Block height2,101,669
Block hash1a9f021f7b0eca4c9d92129ebea96efe033ddab9cbd6d258f8a968590d12ff9d
Time25/04/2026 22:21:04 UTC
Txid3d3e5a7f00389bfc054e63c2b8b34a51773ef216052d025f282f7ef65d27deef
TypeData transaction
Type int200
StatusValid
Confirmations6+
PropertyN/A
NFTNo
DivisibleN/A
SenderxWzvSGpYUPucJaodadUh3yzEmLJGvHUYsP
ReceiverxKutgZdyAPAnHrYE5APQ8NQPBK7DwgWgi6
Transaction fee0.000353 XEP
Certelo
Before you share it, Certelo it.
Certelo verification QR

Proof of existence

This blockchain detail confirms that the SHA-256 fingerprint of the associated file was recorded on the Electra Protocol (XEP) blockchain at the stated UTC date and time. Because the record is immutable, it is strong proof of existence.

About this proof

What it is - A SHA-256 fingerprint is a unique digital fingerprint of a file. If one byte or letter changes, the fingerprint changes completely; collisions are effectively impossible. Learn more: https://en.wikipedia.org/wiki/SHA-2

When it matters - Use it before you publish, pitch, sign, send, or share ideas, designs, photos, contracts, reports, research data, source code, or proposals. It can help support intellectual-property claims by creating strong, independently verifiable proof that this digital file already existed at this date and time. More use cases: https://certelo.io/about#usecases

Where it lives - The fingerprint is recorded on the Electra Protocol (XEP) blockchain, distributed across hundreds of nodes worldwide and not held by CERTELO. Live network map: https://explorer.electraprotocol.network/#map. Verify: https://certelo.io/verify

Proof IDCERT-26042522-1EC9D0C7
Certification date and time UTC2026-04-25 - 22:21 UTC
SHA-2565b03d36a754b810c44fa3a51214d5bba2ab191016e19f0a1023e529b91439c15
BlockchainElectra Protocol (XEP)
Transaction ID3d3e5a7f00389bfc054e63c2b8b34a51773ef216052d025f282f7ef65d27deef
OmniXEP Events

Data

Data typeTEXT
SenderxWzvSGpYUPucJaodadUh3yzEmLJGvHUYsP
ReferencexKutgZdyAPAnHrYE5APQ8NQPBK7DwgWgi6
Text
{
    "doc_hash": "5b03d36a754b810c44fa3a51214d5bba2ab191016e19f0a1023e529b91439c15",
    "doc_id": "CERT-26042522-1EC9D0C7",
    "doc_name": "Screenshot 2026-04-24 at 23.48.03.png"
}
Hex6F6D6E69000000EFBFBD307E237B22646F635F68617368223A2235623033643336613735346238313063343466613361353132313464356262613261623139313031366531396630613130323365353239623931343339633135222C22646F635F6964223A22434552542D32363034323532322D3145433944304337222C22646F635F6E616D65223A2253637265656E73686F7420323032362D30342D32342061742032332E34382E30332E706E67227D
XEP Layer Details
Layer txid3d3e5a7f00389bfc054e63c2b8b34a51773ef216052d025f282f7ef65d27deef
Block height2,101,669
Block hash1a9f021f7b0eca4c9d92129ebea96efe033ddab9cbd6d258f8a968590d12ff9d
Time25/04/2026 22:21:04 UTC
XEP funds flow

Inputs

→

Outputs