Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e0c497599c393f7d3bee87844b0f023f52bf6c41ae60aef18e3823c43314b0e

Tx prefix hash: 2b829200d9d394e2a1649c9a8132bceee4eea11ca79a9a31d6a5dbd18e9aea70
Tx public key: 5d4db0c26db7d32e56baf6b04453ef381ecd8589eeac0784b0aec245bacb278a
Timestamp: 1703451768 Timestamp [UCT]: 2023-12-24 21:02:48 Age [y:d:h:m:s]: 01:085:20:50:15
Block: 920358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322505 RingCT/type: yes/0
Extra: 015d4db0c26db7d32e56baf6b04453ef381ecd8589eeac0784b0aec245bacb278a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b434b481a4f78690544abb28dddac8526f87d1c0c34bc8d665c7a6d29a7eff6 0.600000000000 1378036 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": 920368, "vin": [ { "gen": { "height": 920358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b434b481a4f78690544abb28dddac8526f87d1c0c34bc8d665c7a6d29a7eff6" } } ], "extra": [ 1, 93, 77, 176, 194, 109, 183, 211, 46, 86, 186, 246, 176, 68, 83, 239, 56, 30, 205, 133, 137, 238, 172, 7, 132, 176, 174, 194, 69, 186, 203, 39, 138, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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