Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83b6fa1ff52a3b179c7e689cf29053ed6446cc48e020d284779065e9b3d6989a

Tx prefix hash: 6c75f2ba2e6811ed2be41fd0cd8c9f092055e60650edf1b843fea156070bc0c9
Tx public key: f64e21948965b48762f35f3c6784a2be7d90a30e16a1e3049ecd47de70862fce
Timestamp: 1713469122 Timestamp [UCT]: 2024-04-18 19:38:42 Age [y:d:h:m:s]: 01:038:21:44:00
Block: 1003398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288785 RingCT/type: yes/0
Extra: 01f64e21948965b48762f35f3c6784a2be7d90a30e16a1e3049ecd47de70862fce021100000006e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f8eafae630edb54ced9f933b4dce70b7dc5988230a5af3d9227c628a50c9132 0.600000000000 1463928 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": 1003408, "vin": [ { "gen": { "height": 1003398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f8eafae630edb54ced9f933b4dce70b7dc5988230a5af3d9227c628a50c9132" } } ], "extra": [ 1, 246, 78, 33, 148, 137, 101, 180, 135, 98, 243, 95, 60, 103, 132, 162, 190, 125, 144, 163, 14, 22, 161, 227, 4, 158, 205, 71, 222, 112, 134, 47, 206, 2, 17, 0, 0, 0, 6, 224, 133, 50, 182, 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