Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ac9b080e44b49ed3cc57ca71ce51480c4de89f29fe8f30cccd1781f57c0081f

Tx prefix hash: 5886fb1f794a1ba6b3d5704638fde844a1555d65dc3e8b7b8effd698f2ead8b8
Tx public key: 372f78065900abd5bf99dee18eec3570840b9d9bf9b7e292e3fb2b143fb4e1be
Timestamp: 1754570517 Timestamp [UCT]: 2025-08-07 12:41:57 Age [y:d:h:m:s]: 00:010:05:55:36
Block: 1342135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6539 RingCT/type: yes/0
Extra: 01372f78065900abd5bf99dee18eec3570840b9d9bf9b7e292e3fb2b143fb4e1be0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1399470c398491a538ba35800b65b2c2e5076c1c36fd8799396c3659d4aa6d20 0.600000000000 1829964 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": 1342145, "vin": [ { "gen": { "height": 1342135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1399470c398491a538ba35800b65b2c2e5076c1c36fd8799396c3659d4aa6d20" } } ], "extra": [ 1, 55, 47, 120, 6, 89, 0, 171, 213, 191, 153, 222, 225, 142, 236, 53, 112, 132, 11, 157, 155, 249, 183, 226, 146, 227, 251, 43, 20, 63, 180, 225, 190, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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