Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fcd7d13d9c78d1eecc71d544da2bc46e6be1e9297b93f5bc843f28555f17cc7

Tx prefix hash: 276e3d4e369929f384f201ff46b0e639fa5e60ea99387165b87666f1b24759b0
Tx public key: 59067df63b4ad0e00b23b338edfc06698ddd74b2c59ef0384eafa0d6db43c2f8
Timestamp: 1733412834 Timestamp [UCT]: 2024-12-05 15:33:54 Age [y:d:h:m:s]: 00:140:15:27:22
Block: 1168655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100335 RingCT/type: yes/0
Extra: 0159067df63b4ad0e00b23b338edfc06698ddd74b2c59ef0384eafa0d6db43c2f80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7bd97f6b8f2b63efe05032e3fff917dbfa84d764e21e697d50cbcc302059d1e 0.600000000000 1654366 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": 1168665, "vin": [ { "gen": { "height": 1168655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7bd97f6b8f2b63efe05032e3fff917dbfa84d764e21e697d50cbcc302059d1e" } } ], "extra": [ 1, 89, 6, 125, 246, 59, 74, 208, 224, 11, 35, 179, 56, 237, 252, 6, 105, 141, 221, 116, 178, 197, 158, 240, 56, 78, 175, 160, 214, 219, 67, 194, 248, 2, 17, 0, 0, 0, 2, 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