Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a0e5f91cb3560c5f9c910b48ef98d9ad61be6c094cde35720c7bb911a54596

Tx prefix hash: 9b3532a10eb91a8513d5e63cbe68c14582c63cc8832cf9e5858d7a0cdaee0da1
Tx public key: f86666a635f97ae5dc5d53fd4fa027d0e0c5a37414947f32a5b032d757dfbf88
Timestamp: 1710985550 Timestamp [UCT]: 2024-03-21 01:45:50 Age [y:d:h:m:s]: 01:028:02:59:12
Block: 982837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281070 RingCT/type: yes/0
Extra: 01f86666a635f97ae5dc5d53fd4fa027d0e0c5a37414947f32a5b032d757dfbf880211000000140011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d98f65397cf10379e2a724517d974dcf0dc93fb6b7c89fc654e09d8b58905186 0.600000000000 1442950 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": 982847, "vin": [ { "gen": { "height": 982837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98f65397cf10379e2a724517d974dcf0dc93fb6b7c89fc654e09d8b58905186" } } ], "extra": [ 1, 248, 102, 102, 166, 53, 249, 122, 229, 220, 93, 83, 253, 79, 160, 39, 208, 224, 197, 163, 116, 20, 148, 127, 50, 165, 176, 50, 215, 87, 223, 191, 136, 2, 17, 0, 0, 0, 20, 0, 17, 5, 91, 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