Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cab493cda1678b426adeb1384a747f53b0bbd9b2632000df4d4194b9de994cd

Tx prefix hash: 8ca583fdb54ec7b7affef58d039bf4d917655232ac6587f87975e2da72fba04d
Tx public key: 415d75877a035d822e05983b43435c63be51cfe21b8718d4c00769f42bfa6f28
Timestamp: 1712832508 Timestamp [UCT]: 2024-04-11 10:48:28 Age [y:d:h:m:s]: 00:231:09:45:33
Block: 998107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165688 RingCT/type: yes/0
Extra: 01415d75877a035d822e05983b43435c63be51cfe21b8718d4c00769f42bfa6f2802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 398f197f688b0138b979512a5d105f9384c432ad023fb532ae8e7dc0ea5f61a4 0.600000000000 1458549 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": 998117, "vin": [ { "gen": { "height": 998107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "398f197f688b0138b979512a5d105f9384c432ad023fb532ae8e7dc0ea5f61a4" } } ], "extra": [ 1, 65, 93, 117, 135, 122, 3, 93, 130, 46, 5, 152, 59, 67, 67, 92, 99, 190, 81, 207, 226, 27, 135, 24, 212, 192, 7, 105, 244, 43, 250, 111, 40, 2, 17, 0, 0, 0, 7, 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