Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e43fbbc215f4c918845fd521ab6d2e37ed3efaedd516b232a05a11bfd32505

Tx prefix hash: e1bb7539b288f386a34262e36bb7e629fc1ee0bfebaca4a4696ca33e0b6d6e09
Tx public key: 290cdc9fc3e5fe736d4e6bb4b53bf3a362871be05f3b859f8c5ca31ac9f398ea
Timestamp: 1763873594 Timestamp [UCT]: 2025-11-23 04:53:14 Age [y:d:h:m:s]: 00:066:05:11:03
Block: 1418160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47232 RingCT/type: yes/0
Extra: 01290cdc9fc3e5fe736d4e6bb4b53bf3a362871be05f3b859f8c5ca31ac9f398ea02110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9206f9e286418f68ac725fe9338e4ba635010587a29e1d1b3dfddc84aa0f627f 0.600000000000 1906689 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": 1418170, "vin": [ { "gen": { "height": 1418160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9206f9e286418f68ac725fe9338e4ba635010587a29e1d1b3dfddc84aa0f627f" } } ], "extra": [ 1, 41, 12, 220, 159, 195, 229, 254, 115, 109, 78, 107, 180, 181, 59, 243, 163, 98, 135, 27, 224, 95, 59, 133, 159, 140, 92, 163, 26, 201, 243, 152, 234, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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