Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03533b5a52c3e19b0aef63f1b5372761b3ee3979980a9214227b010b7ede326d

Tx prefix hash: 8d342d4fdd32fbad9412e935868ff136d1151f29b01c2eb65e440f5996394573
Tx public key: f5600f3e3c0aedf831e2d9d3f1c375816375bdc2cb646160927f935b043650aa
Timestamp: 1758959811 Timestamp [UCT]: 2025-09-27 07:56:51 Age [y:d:h:m:s]: 00:011:11:47:49
Block: 1377451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8207 RingCT/type: yes/0
Extra: 01f5600f3e3c0aedf831e2d9d3f1c375816375bdc2cb646160927f935b043650aa0211000000016130ce73000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3c88e82f282d9635152584b7f76a2fd16d993ef470d48c82554f3306b6aaabf 0.600000000000 1865544 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": 1377461, "vin": [ { "gen": { "height": 1377451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3c88e82f282d9635152584b7f76a2fd16d993ef470d48c82554f3306b6aaabf" } } ], "extra": [ 1, 245, 96, 15, 62, 60, 10, 237, 248, 49, 226, 217, 211, 241, 195, 117, 129, 99, 117, 189, 194, 203, 100, 97, 96, 146, 127, 147, 91, 4, 54, 80, 170, 2, 17, 0, 0, 0, 1, 97, 48, 206, 115, 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