Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f259a3f356e2611081a07b5d7f9eec21e715b8eefe3870fefbe87cd5e432018

Tx prefix hash: 60489daed2e589aef92969eff232d59cbbdc9db07776813a1dd62b846c04bbd9
Tx public key: b3b458b4fbc9963c6e9657e5c6a229212f7f6a769ba3064e7228975ccb1e4076
Timestamp: 1731775646 Timestamp [UCT]: 2024-11-16 16:47:26 Age [y:d:h:m:s]: 00:176:16:25:40
Block: 1155075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126130 RingCT/type: yes/0
Extra: 01b3b458b4fbc9963c6e9657e5c6a229212f7f6a769ba3064e7228975ccb1e40760211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef191f57a83af400f940b3fd328496c280057be30fb49b52c62543900ad59e2c 0.600000000000 1640688 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": 1155085, "vin": [ { "gen": { "height": 1155075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef191f57a83af400f940b3fd328496c280057be30fb49b52c62543900ad59e2c" } } ], "extra": [ 1, 179, 180, 88, 180, 251, 201, 150, 60, 110, 150, 87, 229, 198, 162, 41, 33, 47, 127, 106, 118, 155, 163, 6, 78, 114, 40, 151, 92, 203, 30, 64, 118, 2, 17, 0, 0, 0, 3, 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