Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 610a49d59af84e8f77e107b1b807dbbb3cf0252db12671f2fea4308d452be198

Tx prefix hash: df8a987af857edffc3d83aed752f584a543a5a0eba9b2f4c80cb7db3e8e33f7f
Tx public key: e996873b78c051992be9d183612a367a8607c8f7bb3f99c26f3a323ada94ec74
Timestamp: 1749260325 Timestamp [UCT]: 2025-06-07 01:38:45 Age [y:d:h:m:s]: 00:160:04:28:45
Block: 1299582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112173 RingCT/type: yes/0
Extra: 01e996873b78c051992be9d183612a367a8607c8f7bb3f99c26f3a323ada94ec7402110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd68b4e8140f8df94983e8b1de5db54ad525b39c514d530fd750026fa7816387 0.600000000000 1787119 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": 1299592, "vin": [ { "gen": { "height": 1299582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd68b4e8140f8df94983e8b1de5db54ad525b39c514d530fd750026fa7816387" } } ], "extra": [ 1, 233, 150, 135, 59, 120, 192, 81, 153, 43, 233, 209, 131, 97, 42, 54, 122, 134, 7, 200, 247, 187, 63, 153, 194, 111, 58, 50, 58, 218, 148, 236, 116, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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