Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e5ebec3079c8eca9cfe9549e1012ca088e0e75cdae2bd49607ef1001fa0fdb92

Tx prefix hash: 96d0f659e32c38159f1059ae0764db2359bcd3cae1c3b743fe1d3a4df35ed75c
Tx public key: ef4aaaf7531a6e1c1e1e3e7f92dbdef171b9ffee1460f2a0f59b418472440208
Timestamp: 1764788555 Timestamp [UCT]: 2025-12-03 19:02:35 Age [y:d:h:m:s]: 00:018:07:13:51
Block: 1425759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13090 RingCT/type: yes/0
Extra: 01ef4aaaf7531a6e1c1e1e3e7f92dbdef171b9ffee1460f2a0f59b4184724402080211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e55a7517c2edf62cbf571fcbad876768f23c961b24956b16eb5934b652c17142 0.600000000000 1914432 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1425769, "vin": [ { "gen": { "height": 1425759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e55a7517c2edf62cbf571fcbad876768f23c961b24956b16eb5934b652c17142" } } ], "extra": [ 1, 239, 74, 170, 247, 83, 26, 110, 28, 30, 30, 62, 127, 146, 219, 222, 241, 113, 185, 255, 238, 20, 96, 242, 160, 245, 155, 65, 132, 114, 68, 2, 8, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8