Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389b597f048ef3d6b02e44158ad7b3da220e0a4cc46be8e645c16e53bcd72450

Tx prefix hash: a1b3a2933ab2b01161368e4e5d59e86a888430f8793171d7a62cbd7f79bfadd2
Tx public key: ae7542e4ee8c8ee04fb6767a3450f32c013e9d2883a80c349a32112fcfe2eec1
Timestamp: 1729188359 Timestamp [UCT]: 2024-10-17 18:05:59 Age [y:d:h:m:s]: 00:021:10:07:47
Block: 1133737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15255 RingCT/type: yes/0
Extra: 01ae7542e4ee8c8ee04fb6767a3450f32c013e9d2883a80c349a32112fcfe2eec1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6cb3ab995e91185cc262b7f794c37f4a82b8ad8134907b240ab661a86039d8e 0.600000000000 1616928 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": 1133747, "vin": [ { "gen": { "height": 1133737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6cb3ab995e91185cc262b7f794c37f4a82b8ad8134907b240ab661a86039d8e" } } ], "extra": [ 1, 174, 117, 66, 228, 238, 140, 142, 224, 79, 182, 118, 122, 52, 80, 243, 44, 1, 62, 157, 40, 131, 168, 12, 52, 154, 50, 17, 47, 207, 226, 238, 193, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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