Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8279d6511127051be85e9725f26e6c8aa9b3d7c6be6908080ea1b412d84841a

Tx prefix hash: 32876899c431430a658e40b74da62e40474395e3dfac7622ed5f1a07660cac1b
Tx public key: 3b21ca321a5196da05c2d517d59c1a8bc34b8cd9f578b50985043a1b71c239bf
Timestamp: 1760561116 Timestamp [UCT]: 2025-10-15 20:45:16 Age [y:d:h:m:s]: 00:083:15:03:52
Block: 1390708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59883 RingCT/type: yes/0
Extra: 013b21ca321a5196da05c2d517d59c1a8bc34b8cd9f578b50985043a1b71c239bf0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55e8a0ad54d8470bb33570aabce9d55e286bc0a7995cad45e8f9cc2b9ba6fa4a 0.600000000000 1878955 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": 1390718, "vin": [ { "gen": { "height": 1390708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55e8a0ad54d8470bb33570aabce9d55e286bc0a7995cad45e8f9cc2b9ba6fa4a" } } ], "extra": [ 1, 59, 33, 202, 50, 26, 81, 150, 218, 5, 194, 213, 23, 213, 156, 26, 139, 195, 75, 140, 217, 245, 120, 181, 9, 133, 4, 58, 27, 113, 194, 57, 191, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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