Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb1b484797dfee921b8f1e55166fbec18a8efdcdaff165772907ba395036e87

Tx prefix hash: 581f9b2118b2c9b4bcdb2f9ffe960072f79bd9b54e55aa3d9545b89c5718d6f3
Tx public key: 3bb7e884e1dbf389dfc88b002a50af3fc1dd760ad8cecb638ab734d47246a00c
Timestamp: 1766477057 Timestamp [UCT]: 2025-12-23 08:04:17 Age [y:d:h:m:s]: 00:037:05:06:07
Block: 1439734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26462 RingCT/type: yes/0
Extra: 013bb7e884e1dbf389dfc88b002a50af3fc1dd760ad8cecb638ab734d47246a00c02110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bcd3c06bda58d50a31b5a9a3011a6587feb8ee5e62a3d2c472a3d2a95ad5a2b 0.600000000000 1928581 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": 1439744, "vin": [ { "gen": { "height": 1439734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bcd3c06bda58d50a31b5a9a3011a6587feb8ee5e62a3d2c472a3d2a95ad5a2b" } } ], "extra": [ 1, 59, 183, 232, 132, 225, 219, 243, 137, 223, 200, 139, 0, 42, 80, 175, 63, 193, 221, 118, 10, 216, 206, 203, 99, 138, 183, 52, 212, 114, 70, 160, 12, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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