Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c0f08920f40b06e34bb77ef6176af0493cd425a23a8a0e85aa948479b4c5c0

Tx prefix hash: 6638c6b5a9c499ae496384be92d05f676962880b8151d06576a97658b9d1c1e4
Tx public key: a105e9b9ec421f592905e256298acd8ab73ef0198fe6f55b3a5e3d7213694a53
Timestamp: 1638463010 Timestamp [UCT]: 2021-12-02 16:36:50 Age [y:d:h:m:s]: 03:158:03:08:20
Block: 386917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 891733 RingCT/type: yes/0
Extra: 01a105e9b9ec421f592905e256298acd8ab73ef0198fe6f55b3a5e3d7213694a53021100000006379224c2000000000000000000

1 output(s) for total of 32.061492301000 dcy

stealth address amount amount idx
00: 0b9b72f41d331998f389c06c386cc6c50d5f7824748e4a0bad0c61c464644a65 32.061492301000 780496 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": 386927, "vin": [ { "gen": { "height": 386917 } } ], "vout": [ { "amount": 32061492301, "target": { "key": "0b9b72f41d331998f389c06c386cc6c50d5f7824748e4a0bad0c61c464644a65" } } ], "extra": [ 1, 161, 5, 233, 185, 236, 66, 31, 89, 41, 5, 226, 86, 41, 138, 205, 138, 183, 62, 240, 25, 143, 230, 245, 91, 58, 94, 61, 114, 19, 105, 74, 83, 2, 17, 0, 0, 0, 6, 55, 146, 36, 194, 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