Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c514b75ed26d61a035fcf86f30a99396e14cd6cd0cc96a821401223df40de681

Tx prefix hash: 45be5a77b05ff2ff5fb2757979d4d013e89bf694335212effd3aaa09d5a71eac
Tx public key: c9742dc668166324fae057e4defe1fbe0039a3e71fdaefe939b8b191b8f8b1be
Timestamp: 1761264748 Timestamp [UCT]: 2025-10-24 00:12:28 Age [y:d:h:m:s]: 00:091:11:57:00
Block: 1396556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65365 RingCT/type: yes/0
Extra: 01c9742dc668166324fae057e4defe1fbe0039a3e71fdaefe939b8b191b8f8b1be021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6afae3986438a5519710ce9a3e32174c9389517416358ee5d590d17e8df3c8a 0.600000000000 1884843 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": 1396566, "vin": [ { "gen": { "height": 1396556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6afae3986438a5519710ce9a3e32174c9389517416358ee5d590d17e8df3c8a" } } ], "extra": [ 1, 201, 116, 45, 198, 104, 22, 99, 36, 250, 224, 87, 228, 222, 254, 31, 190, 0, 57, 163, 231, 31, 218, 239, 233, 57, 184, 177, 145, 184, 248, 177, 190, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 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