Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d947c3d84875bedb2ca0dd442a8e130b5cd167a66cdd723340a3476624d77ae

Tx prefix hash: 16b8d7a38d88194ab5ca66f3e51d5e959eb2ffdbb2a8a9176645ff0520c1ff60
Tx public key: 6813d31d2490e95d87ac6833dd6975e76d16ccb4fcec01b976d10f30d9f9d194
Timestamp: 1706038489 Timestamp [UCT]: 2024-01-23 19:34:49 Age [y:d:h:m:s]: 01:056:03:00:09
Block: 941783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301225 RingCT/type: yes/0
Extra: 016813d31d2490e95d87ac6833dd6975e76d16ccb4fcec01b976d10f30d9f9d19402110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c50510f780b69e5a26bc5fc50699a52912333742fb0fa0338d9bc4aa475e0204 0.600000000000 1399939 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": 941793, "vin": [ { "gen": { "height": 941783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c50510f780b69e5a26bc5fc50699a52912333742fb0fa0338d9bc4aa475e0204" } } ], "extra": [ 1, 104, 19, 211, 29, 36, 144, 233, 93, 135, 172, 104, 51, 221, 105, 117, 231, 109, 22, 204, 180, 252, 236, 1, 185, 118, 209, 15, 48, 217, 249, 209, 148, 2, 17, 0, 0, 0, 14, 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