Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9586da87f38962e425ee387893f263feba664d55421c6a12b6ee2c556c440af7

Tx prefix hash: 5870cb0e120eeae125630ea63ae13952b90110a7c4f6d8df4811af75465abdf5
Tx public key: 14d38cf13a92e39e154081aead2b03ecea1c3f8c661acab599fe6a5ce9af82d9
Timestamp: 1737257591 Timestamp [UCT]: 2025-01-19 03:33:11 Age [y:d:h:m:s]: 00:150:03:53:12
Block: 1200442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107057 RingCT/type: yes/0
Extra: 0114d38cf13a92e39e154081aead2b03ecea1c3f8c661acab599fe6a5ce9af82d9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5df94508d02e9f284049e13cfa7b73ddaf63a5328624c277d9356ce1f522460 0.600000000000 1687085 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": 1200452, "vin": [ { "gen": { "height": 1200442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5df94508d02e9f284049e13cfa7b73ddaf63a5328624c277d9356ce1f522460" } } ], "extra": [ 1, 20, 211, 140, 241, 58, 146, 227, 158, 21, 64, 129, 174, 173, 43, 3, 236, 234, 28, 63, 140, 102, 26, 202, 181, 153, 254, 106, 92, 233, 175, 130, 217, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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