Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c3a14cc0ee1bb97d458a62acd5be5ddd33fa65b54a7a6344704f830bb0a9880

Tx prefix hash: 12b5eca71a7600fb500aacfdbb89eeab6fb99ae225769de330e136d8efad3656
Tx public key: 2896ae4b0edb631c8dc9b49f54f78063565a22a9465f59c8fb34996e9670bfae
Timestamp: 1751824035 Timestamp [UCT]: 2025-07-06 17:47:15 Age [y:d:h:m:s]: 00:131:02:53:08
Block: 1320064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92129 RingCT/type: yes/0
Extra: 012896ae4b0edb631c8dc9b49f54f78063565a22a9465f59c8fb34996e9670bfae021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5c535356d48a7e208d45f807631b8327c7365535b797b9557400b5cde35766b 0.600000000000 1807759 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": 1320074, "vin": [ { "gen": { "height": 1320064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5c535356d48a7e208d45f807631b8327c7365535b797b9557400b5cde35766b" } } ], "extra": [ 1, 40, 150, 174, 75, 14, 219, 99, 28, 141, 201, 180, 159, 84, 247, 128, 99, 86, 90, 34, 169, 70, 95, 89, 200, 251, 52, 153, 110, 150, 112, 191, 174, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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