Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2971fb614bafb2af4cf252b8063cbdc40d436448e5e297666e4e4e99b873d48

Tx prefix hash: 9b913c7fe6f5f9aeeeab8775034300a8376876e9a6c04389a52b544cf20501f3
Tx public key: b42975cfaec3ab2f598faef0385e6ab277b825b89c03a84ff557bff14d58aa9e
Timestamp: 1763632851 Timestamp [UCT]: 2025-11-20 10:00:51 Age [y:d:h:m:s]: 00:036:03:02:54
Block: 1416155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25873 RingCT/type: yes/0
Extra: 01b42975cfaec3ab2f598faef0385e6ab277b825b89c03a84ff557bff14d58aa9e0211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b103caa70881b0e8b8f0d3c017ddc6045dc5ac4533290f4e1048485565d76bf4 0.600000000000 1904674 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": 1416165, "vin": [ { "gen": { "height": 1416155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b103caa70881b0e8b8f0d3c017ddc6045dc5ac4533290f4e1048485565d76bf4" } } ], "extra": [ 1, 180, 41, 117, 207, 174, 195, 171, 47, 89, 143, 174, 240, 56, 94, 106, 178, 119, 184, 37, 184, 156, 3, 168, 79, 245, 87, 191, 241, 77, 88, 170, 158, 2, 17, 0, 0, 0, 4, 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