Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a9442f6b71b2223c8a8b8fac619e1694fd9b3ef9835b9220c3d08145a9cac44

Tx prefix hash: a1d76c810ef49035ad8195f104715059a42414d70617742d2ca8105eb965a8b9
Tx public key: 614276da0f048422511d89edbba1c7cb5e8fd078233e4ed60c43d320c899bd5e
Timestamp: 1720017318 Timestamp [UCT]: 2024-07-03 14:35:18 Age [y:d:h:m:s]: 00:270:16:23:43
Block: 1057699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193391 RingCT/type: yes/0
Extra: 01614276da0f048422511d89edbba1c7cb5e8fd078233e4ed60c43d320c899bd5e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80e5e3fbf6e9227307136208f429fdfa7c9fdc109e7603242e41d841bb4a2ddb 0.600000000000 1528138 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": 1057709, "vin": [ { "gen": { "height": 1057699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80e5e3fbf6e9227307136208f429fdfa7c9fdc109e7603242e41d841bb4a2ddb" } } ], "extra": [ 1, 97, 66, 118, 218, 15, 4, 132, 34, 81, 29, 137, 237, 187, 161, 199, 203, 94, 143, 208, 120, 35, 62, 78, 214, 12, 67, 211, 32, 200, 153, 189, 94, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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