Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9115d5bf0e60d8885b2605ea5a04b82bfc02e0b188981512c53a791d2a8cfec7

Tx prefix hash: 53c5e67a62fdf2c8857d24543d3b172081a90a5e4dcdd93bc0acacc22f60f742
Tx public key: a2874cadc73c69f7715a162f04784f63f4688d669c22d5a11e8f7da725d750ae
Timestamp: 1737044937 Timestamp [UCT]: 2025-01-16 16:28:57 Age [y:d:h:m:s]: 00:153:20:33:26
Block: 1198717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109655 RingCT/type: yes/0
Extra: 01a2874cadc73c69f7715a162f04784f63f4688d669c22d5a11e8f7da725d750ae0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 358dc1453d44c1cf206e41d47bdb1e7ba8ae691f560ec76a016ef1735591f810 0.600000000000 1685344 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": 1198727, "vin": [ { "gen": { "height": 1198717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "358dc1453d44c1cf206e41d47bdb1e7ba8ae691f560ec76a016ef1735591f810" } } ], "extra": [ 1, 162, 135, 76, 173, 199, 60, 105, 247, 113, 90, 22, 47, 4, 120, 79, 99, 244, 104, 141, 102, 156, 34, 213, 161, 30, 143, 125, 167, 37, 215, 80, 174, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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