Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689bdc7a5dc42d2364f738b62cbcba0758f19d24dbe9c33988d69731821bab3b

Tx prefix hash: 7444c91dd2ba9157c0af552f6486d96fae7d5af8049ee7de4c290699feca0d13
Tx public key: 0b3fc81828ccdf539716f7563b571022b47d8cd5fd8ab0ca4efb30b63df933aa
Timestamp: 1726858123 Timestamp [UCT]: 2024-09-20 18:48:43 Age [y:d:h:m:s]: 00:244:07:02:45
Block: 1114407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174464 RingCT/type: yes/0
Extra: 010b3fc81828ccdf539716f7563b571022b47d8cd5fd8ab0ca4efb30b63df933aa021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7be0b8e3b08d637b3975edfc895876be9695aba598d85d494d5bf7a3ab68645e 0.600000000000 1594208 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": 1114417, "vin": [ { "gen": { "height": 1114407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7be0b8e3b08d637b3975edfc895876be9695aba598d85d494d5bf7a3ab68645e" } } ], "extra": [ 1, 11, 63, 200, 24, 40, 204, 223, 83, 151, 22, 247, 86, 59, 87, 16, 34, 180, 125, 140, 213, 253, 138, 176, 202, 78, 251, 48, 182, 61, 249, 51, 170, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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