Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02e42c08c753d322b018ebf2b379781b3134719a2aebb6d379e16c44be06d0f2

Tx prefix hash: 698c2a549aa1ca3060c35b8b766941625e7342ab25068e9485e8cce787e1a423
Tx public key: fd57d7cad305f174e6d8e498d45b45c42e943f3b6ed8380f62a59f0f25409952
Timestamp: 1711230540 Timestamp [UCT]: 2024-03-23 21:49:00 Age [y:d:h:m:s]: 00:292:22:29:34
Block: 984877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209668 RingCT/type: yes/0
Extra: 01fd57d7cad305f174e6d8e498d45b45c42e943f3b6ed8380f62a59f0f2540995202110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 472eacfdac44344f7d351aeef3a3216f31017fcafef7bbf71876fc815b6699b8 0.600000000000 1445050 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": 984887, "vin": [ { "gen": { "height": 984877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "472eacfdac44344f7d351aeef3a3216f31017fcafef7bbf71876fc815b6699b8" } } ], "extra": [ 1, 253, 87, 215, 202, 211, 5, 241, 116, 230, 216, 228, 152, 212, 91, 69, 196, 46, 148, 63, 59, 110, 216, 56, 15, 98, 165, 159, 15, 37, 64, 153, 82, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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