Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0118401bbb14d1625f43bc97515a521c2c408ed2e0875caa767165a9faaa79

Tx prefix hash: 88033ace66b5c2ab6c9b39c3e5dc1124a6fd07e7b81923aa5455a1b00fab5a56
Tx public key: ff616a9dbb358f12597799ebf984bbbccbe4fac1917b0be65c3e53a78b939433
Timestamp: 1710927393 Timestamp [UCT]: 2024-03-20 09:36:33 Age [y:d:h:m:s]: 00:364:01:29:17
Block: 982363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260299 RingCT/type: yes/0
Extra: 01ff616a9dbb358f12597799ebf984bbbccbe4fac1917b0be65c3e53a78b93943302110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 722846d1cd68fc8b57cc80209c3d837a376fb43fa25e9dcad1a7e2b0a72d9d09 0.600000000000 1442468 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": 982373, "vin": [ { "gen": { "height": 982363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722846d1cd68fc8b57cc80209c3d837a376fb43fa25e9dcad1a7e2b0a72d9d09" } } ], "extra": [ 1, 255, 97, 106, 157, 187, 53, 143, 18, 89, 119, 153, 235, 249, 132, 187, 188, 203, 228, 250, 193, 145, 123, 11, 230, 92, 62, 83, 167, 139, 147, 148, 51, 2, 17, 0, 0, 0, 9, 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