Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c88289aec3552bfd6e8ad498fc1b50b8f877d3e7e59307b5a8d03273e9f78c

Tx prefix hash: 016c13d6db044cbdf742ad7cfd3bb9560da7a579809c946b144e8dd1e75463de
Tx public key: 4f61ff50fcf9b41d6ec5f1ed5c9c074166565307ae4ff1f7f5d1920b21a44300
Timestamp: 1732532860 Timestamp [UCT]: 2024-11-25 11:07:40 Age [y:d:h:m:s]: 00:156:05:26:16
Block: 1161357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111478 RingCT/type: yes/0
Extra: 014f61ff50fcf9b41d6ec5f1ed5c9c074166565307ae4ff1f7f5d1920b21a4430002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8beb99aaa9b477337eb7c2368632925f9e8c243cc7d9bda97901eecc2c09768c 0.600000000000 1647010 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": 1161367, "vin": [ { "gen": { "height": 1161357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8beb99aaa9b477337eb7c2368632925f9e8c243cc7d9bda97901eecc2c09768c" } } ], "extra": [ 1, 79, 97, 255, 80, 252, 249, 180, 29, 110, 197, 241, 237, 92, 156, 7, 65, 102, 86, 83, 7, 174, 79, 241, 247, 245, 209, 146, 11, 33, 164, 67, 0, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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