Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a04cca7786b7d0b263bf858482d662af2e5a889d5541110a1dd9c9d1aea6124

Tx prefix hash: 2a62ed0d55c3526adb90d4b463913da29d2e85de074b88c2ec5496c3b967f15a
Tx public key: 9f96adce930944340ab67347f2dd2e56777bb9d63214dbbaa14e01e8f0a67d96
Timestamp: 1676496776 Timestamp [UCT]: 2023-02-15 21:32:56 Age [y:d:h:m:s]: 02:051:04:08:32
Block: 697779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558156 RingCT/type: yes/0
Extra: 019f96adce930944340ab67347f2dd2e56777bb9d63214dbbaa14e01e8f0a67d9602110000000274b6d784000000000000000000

1 output(s) for total of 2.992047113000 dcy

stealth address amount amount idx
00: d88cba07fd9c52016cb3f6090c183c96cbbef72826241e101cabbe5e0db65ad8 2.992047113000 1141028 of 0

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": 697789, "vin": [ { "gen": { "height": 697779 } } ], "vout": [ { "amount": 2992047113, "target": { "key": "d88cba07fd9c52016cb3f6090c183c96cbbef72826241e101cabbe5e0db65ad8" } } ], "extra": [ 1, 159, 150, 173, 206, 147, 9, 68, 52, 10, 182, 115, 71, 242, 221, 46, 86, 119, 123, 185, 214, 50, 20, 219, 186, 161, 78, 1, 232, 240, 166, 125, 150, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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