Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ebdea0b5b29fc52ed2489b71ddab9a03f65d76826a48a1274b6cbf140f8ede

Tx prefix hash: 288f5f35b843e2b939b581a2a800b43074f7e71693a4d2c042de7452209019fd
Tx public key: 5f15ff8480dc9c8e91ad5003d25effffd8ea2f0d155b9d12ec5a1993b326d277
Timestamp: 1697110236 Timestamp [UCT]: 2023-10-12 11:30:36 Age [y:d:h:m:s]: 01:176:04:32:44
Block: 868002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386942 RingCT/type: yes/0
Extra: 015f15ff8480dc9c8e91ad5003d25effffd8ea2f0d155b9d12ec5a1993b326d2770211000000234b8f5122000000000000000000

1 output(s) for total of 0.816486634000 dcy

stealth address amount amount idx
00: 8ab0fd765231e4e15394fa7774bd7be6fd33ee8a18a3c718aa44de55af63538c 0.816486634000 1322747 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": 868012, "vin": [ { "gen": { "height": 868002 } } ], "vout": [ { "amount": 816486634, "target": { "key": "8ab0fd765231e4e15394fa7774bd7be6fd33ee8a18a3c718aa44de55af63538c" } } ], "extra": [ 1, 95, 21, 255, 132, 128, 220, 156, 142, 145, 173, 80, 3, 210, 94, 255, 255, 216, 234, 47, 13, 21, 91, 157, 18, 236, 90, 25, 147, 179, 38, 210, 119, 2, 17, 0, 0, 0, 35, 75, 143, 81, 34, 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