Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2d8fd6420361c31acf9100b393a8e8b7f6629bac11f9528560b980baa26e3d

Tx prefix hash: 37979cc46bb64b31394bb748259b114144a3ff2a85faec2dd853b964092e8289
Tx public key: f409d66845a8a1a3a948d242effbec6c4b70ac41aa97c5528d07b05e751678c9
Timestamp: 1657802042 Timestamp [UCT]: 2022-07-14 12:34:02 Age [y:d:h:m:s]: 02:173:03:23:59
Block: 543598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645089 RingCT/type: yes/0
Extra: 01f409d66845a8a1a3a948d242effbec6c4b70ac41aa97c5528d07b05e751678c9021100000007a8c141c5000000000000000000

1 output(s) for total of 9.701397721000 dcy

stealth address amount amount idx
00: f73b614b58d389f837e83a7496b722a4bfa90c759f34aa78927fda358821d87f 9.701397721000 974285 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": 543608, "vin": [ { "gen": { "height": 543598 } } ], "vout": [ { "amount": 9701397721, "target": { "key": "f73b614b58d389f837e83a7496b722a4bfa90c759f34aa78927fda358821d87f" } } ], "extra": [ 1, 244, 9, 214, 104, 69, 168, 161, 163, 169, 72, 210, 66, 239, 251, 236, 108, 75, 112, 172, 65, 170, 151, 197, 82, 141, 7, 176, 94, 117, 22, 120, 201, 2, 17, 0, 0, 0, 7, 168, 193, 65, 197, 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