Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7952814f01181f0e37cdd5aa1e70e7ccb33a4008b1da25e90401d8a4231755a8

Tx prefix hash: 4a435355730d9b2f0cdf1a1d473544016cb25bd3cb22b6d5e7fffdc1fefdfd2f
Tx public key: a459333dba3d8206113c535a55d45cddc6689dce2f5c3f034e60163d36e18fd4
Timestamp: 1751414293 Timestamp [UCT]: 2025-07-01 23:58:13 Age [y:d:h:m:s]: 00:136:05:58:37
Block: 1316869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95596 RingCT/type: yes/0
Extra: 01a459333dba3d8206113c535a55d45cddc6689dce2f5c3f034e60163d36e18fd402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01af112f6ae80bb72135725a2fd2663c8f4c3aae625d4effe4a28cd9ba135267 0.600000000000 1804532 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": 1316879, "vin": [ { "gen": { "height": 1316869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01af112f6ae80bb72135725a2fd2663c8f4c3aae625d4effe4a28cd9ba135267" } } ], "extra": [ 1, 164, 89, 51, 61, 186, 61, 130, 6, 17, 60, 83, 90, 85, 212, 92, 221, 198, 104, 157, 206, 47, 92, 63, 3, 78, 96, 22, 61, 54, 225, 143, 212, 2, 17, 0, 0, 0, 1, 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