Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9de767b3b704fef997b5c53668242eb218b95f3bca2d337ca0f48b71b69e030b

Tx prefix hash: afef8c84709b04b4d0db941d0a3914d060efc86a545b0ecbe90ee67f99cd0a73
Tx public key: df7f1aef7f8ef9822ce96099c1ef99c5270b1e2b6eda5e60783ad3a988b742ef
Timestamp: 1719695195 Timestamp [UCT]: 2024-06-29 21:06:35 Age [y:d:h:m:s]: 01:132:13:00:59
Block: 1055018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353277 RingCT/type: yes/0
Extra: 01df7f1aef7f8ef9822ce96099c1ef99c5270b1e2b6eda5e60783ad3a988b742ef02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91d998b30ee4add445338311c24feadee0cfd291c358b8b9a77da1603b27b91c 0.600000000000 1525411 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": 1055028, "vin": [ { "gen": { "height": 1055018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91d998b30ee4add445338311c24feadee0cfd291c358b8b9a77da1603b27b91c" } } ], "extra": [ 1, 223, 127, 26, 239, 127, 142, 249, 130, 44, 233, 96, 153, 193, 239, 153, 197, 39, 11, 30, 43, 110, 218, 94, 96, 120, 58, 211, 169, 136, 183, 66, 239, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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