Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495ec446a6d5301041181e2d9a854343eb76926ea941314fbd68f61b1840e8de

Tx prefix hash: 3c7efba986146c8ee4286f5724a2614567f623069c678e38a7f5bf0753ad9705
Tx public key: df67283d540fc6edb0d370f57c68d53ee3cc9fcf0dc957ca77689914040ae11e
Timestamp: 1711300849 Timestamp [UCT]: 2024-03-24 17:20:49 Age [y:d:h:m:s]: 01:009:10:15:07
Block: 985457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267675 RingCT/type: yes/0
Extra: 01df67283d540fc6edb0d370f57c68d53ee3cc9fcf0dc957ca77689914040ae11e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fe3b411ca3b4b7f1c29552a6906407cb65d5b1aa615d85a1eae072c3eb63d8e 0.600000000000 1445668 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": 985467, "vin": [ { "gen": { "height": 985457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fe3b411ca3b4b7f1c29552a6906407cb65d5b1aa615d85a1eae072c3eb63d8e" } } ], "extra": [ 1, 223, 103, 40, 61, 84, 15, 198, 237, 176, 211, 112, 245, 124, 104, 213, 62, 227, 204, 159, 207, 13, 201, 87, 202, 119, 104, 153, 20, 4, 10, 225, 30, 2, 17, 0, 0, 0, 2, 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