Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e04c6743063bce480b2e0176712c03bee02c19d7d212359e30382c5e868c20

Tx prefix hash: 0d05119ff2a8cc260c6b967ccad4e72b3a2343715c38116298f54cd1c13c9f00
Tx public key: bfc517e91e273a7c5fee7036301ac9ba61b7738995f67c13ff26055d1a3f42d1
Timestamp: 1734847847 Timestamp [UCT]: 2024-12-22 06:10:47 Age [y:d:h:m:s]: 00:112:00:36:45
Block: 1180557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79831 RingCT/type: yes/0
Extra: 01bfc517e91e273a7c5fee7036301ac9ba61b7738995f67c13ff26055d1a3f42d102110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e8584d3f8c2e005c285d590d05a04ce9d30196e7fd977cd5efe3d836812b38b 0.600000000000 1666970 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": 1180567, "vin": [ { "gen": { "height": 1180557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e8584d3f8c2e005c285d590d05a04ce9d30196e7fd977cd5efe3d836812b38b" } } ], "extra": [ 1, 191, 197, 23, 233, 30, 39, 58, 124, 95, 238, 112, 54, 48, 26, 201, 186, 97, 183, 115, 137, 149, 246, 124, 19, 255, 38, 5, 93, 26, 63, 66, 209, 2, 17, 0, 0, 0, 10, 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