Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f406448e082f2f79d434a9f78b39e51ddf5d60b075d518d682de69304db90de

Tx prefix hash: b266a7478b254b40cbfa25a6afe68a9d21dbfe3092fcc2f97ff2605c5af7345c
Tx public key: 0f54941264f0f1680af854e5d732c489e629f2fabf3302d9aed1e4670c8806e3
Timestamp: 1760795026 Timestamp [UCT]: 2025-10-18 13:43:46 Age [y:d:h:m:s]: 00:080:22:30:18
Block: 1392663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57944 RingCT/type: yes/0
Extra: 010f54941264f0f1680af854e5d732c489e629f2fabf3302d9aed1e4670c8806e3021100000008df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96e4aef40c29d5bfdea00816d660eed445a884afc85be254e334cf061e44c507 0.600000000000 1880916 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": 1392673, "vin": [ { "gen": { "height": 1392663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96e4aef40c29d5bfdea00816d660eed445a884afc85be254e334cf061e44c507" } } ], "extra": [ 1, 15, 84, 148, 18, 100, 240, 241, 104, 10, 248, 84, 229, 215, 50, 196, 137, 230, 41, 242, 250, 191, 51, 2, 217, 174, 209, 228, 103, 12, 136, 6, 227, 2, 17, 0, 0, 0, 8, 223, 90, 36, 122, 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