Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb2ff3e4d4fa95dfb32b6ac923fa61df25ff614b1eb80be198fab3e588748fcb

Tx prefix hash: 010efb67ba014325dba3647323cba408d9a39f9626a53a29a8801681c12c8777
Tx public key: a324070eafdd43edd59d9cf7ac1f7ef1f5bb079d44ed32362c49aa8be22e2e4e
Timestamp: 1760522424 Timestamp [UCT]: 2025-10-15 10:00:24 Age [y:d:h:m:s]: 00:078:18:55:40
Block: 1390395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56413 RingCT/type: yes/0
Extra: 01a324070eafdd43edd59d9cf7ac1f7ef1f5bb079d44ed32362c49aa8be22e2e4e0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3af4c953665f013c47b2744c3fbafe5997c9895fb009ff991a08b69ca3e39f94 0.600000000000 1878638 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": 1390405, "vin": [ { "gen": { "height": 1390395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3af4c953665f013c47b2744c3fbafe5997c9895fb009ff991a08b69ca3e39f94" } } ], "extra": [ 1, 163, 36, 7, 14, 175, 221, 67, 237, 213, 157, 156, 247, 172, 31, 126, 241, 245, 187, 7, 157, 68, 237, 50, 54, 44, 73, 170, 139, 226, 46, 46, 78, 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