Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5964821950ec8be55b6b91bc9e69a227dfa2cc5c23c68fefebf3d439edccd125

Tx prefix hash: 036af2bf63813a4e17d1ebbbae080be414cb7c335d236d1c6fd954983ca2d041
Tx public key: 515796b774f53332421a84a8f508caf11b057bd2a2744c58e94c67fce11f5055
Timestamp: 1751376487 Timestamp [UCT]: 2025-07-01 13:28:07 Age [y:d:h:m:s]: 00:140:22:02:54
Block: 1316554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98934 RingCT/type: yes/0
Extra: 01515796b774f53332421a84a8f508caf11b057bd2a2744c58e94c67fce11f5055021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68775414c276130f61c528a13d841b233036a6c05993f72cc178a4ba8a71e039 0.600000000000 1804215 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": 1316564, "vin": [ { "gen": { "height": 1316554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68775414c276130f61c528a13d841b233036a6c05993f72cc178a4ba8a71e039" } } ], "extra": [ 1, 81, 87, 150, 183, 116, 245, 51, 50, 66, 26, 132, 168, 245, 8, 202, 241, 27, 5, 123, 210, 162, 116, 76, 88, 233, 76, 103, 252, 225, 31, 80, 85, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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