Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99a725534d3b32058e3eb8113f735a2dc5b22e2a61806d1cba15019a98c5099e

Tx prefix hash: 0d11465089efe4f073f252c45574b7b1334e8a7afb65aabba1688804ceee9191
Tx public key: 0f9c66464b1ebd30e46ca61ce335b272b77f87022f9678c7e7c164e87d370fc2
Timestamp: 1700636312 Timestamp [UCT]: 2023-11-22 06:58:32 Age [y:d:h:m:s]: 01:131:20:03:32
Block: 897012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355384 RingCT/type: yes/0
Extra: 010f9c66464b1ebd30e46ca61ce335b272b77f87022f9678c7e7c164e87d370fc202110000000375e3f0e9000000000000000000

1 output(s) for total of 0.654375249000 dcy

stealth address amount amount idx
00: dc3987382f365a1be8961e77be58638c94e0b177964a2dd39f57eeb2d0ab3798 0.654375249000 1353365 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": 897022, "vin": [ { "gen": { "height": 897012 } } ], "vout": [ { "amount": 654375249, "target": { "key": "dc3987382f365a1be8961e77be58638c94e0b177964a2dd39f57eeb2d0ab3798" } } ], "extra": [ 1, 15, 156, 102, 70, 75, 30, 189, 48, 228, 108, 166, 28, 227, 53, 178, 114, 183, 127, 135, 2, 47, 150, 120, 199, 231, 193, 100, 232, 125, 55, 15, 194, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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