Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2ec7266777653fea09e0a9f718a637719a04491d7c6230168ada8a2a9065a11

Tx prefix hash: efa0c89c125813d8823e523f15025566339949e6fb7c8acabb227264a5a33243
Tx public key: 5417eda2c4ea2c37d6dbe14c0ca0be876f71b0f8c75d476aec908842f19d6aac
Timestamp: 1709624838 Timestamp [UCT]: 2024-03-05 07:47:18 Age [y:d:h:m:s]: 00:356:22:07:31
Block: 971546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255188 RingCT/type: yes/0
Extra: 015417eda2c4ea2c37d6dbe14c0ca0be876f71b0f8c75d476aec908842f19d6aac02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f890558a35a7eaf1db20c36999e4c659ea20560ddc5063c165a6b015032308e8 0.600000000000 1431443 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": 971556, "vin": [ { "gen": { "height": 971546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f890558a35a7eaf1db20c36999e4c659ea20560ddc5063c165a6b015032308e8" } } ], "extra": [ 1, 84, 23, 237, 162, 196, 234, 44, 55, 214, 219, 225, 76, 12, 160, 190, 135, 111, 113, 176, 248, 199, 93, 71, 106, 236, 144, 136, 66, 241, 157, 106, 172, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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