Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e07c19f05d04b36c62dc92c3c51350afc8e680c24fdc3d9dc2ed3b9829c528f

Tx prefix hash: 5de4c7fa977292a475a29a0fb56eae1c34449d94018c7c60548a8ab54f4011ec
Tx public key: 344ad62bf3899d294771af66c1745bbc62f42cf2980e8fbba0df239cf29a66dc
Timestamp: 1761855886 Timestamp [UCT]: 2025-10-30 20:24:46 Age [y:d:h:m:s]: 00:009:20:09:11
Block: 1401454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7038 RingCT/type: yes/0
Extra: 01344ad62bf3899d294771af66c1745bbc62f42cf2980e8fbba0df239cf29a66dc02110000001925a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b95fd1b7886f7f60679ed872d08e1fed7de139779dbf73cd26f86be37fb2ea 0.600000000000 1889773 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": 1401464, "vin": [ { "gen": { "height": 1401454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b95fd1b7886f7f60679ed872d08e1fed7de139779dbf73cd26f86be37fb2ea" } } ], "extra": [ 1, 52, 74, 214, 43, 243, 137, 157, 41, 71, 113, 175, 102, 193, 116, 91, 188, 98, 244, 44, 242, 152, 14, 143, 187, 160, 223, 35, 156, 242, 154, 102, 220, 2, 17, 0, 0, 0, 25, 37, 163, 90, 15, 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