Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b6e9adeb0058e8c4982efd23b7e88a75cb7c39cfb7ce188f402c78bc4c6a238

Tx prefix hash: 9ff0301e463a84673199213dd3e625d55e8b7aebfc2d6d62cd7a520110b153be
Tx public key: 03ef6bf795544a4a164f9837e5c8a2e4f1722b9f273787335cef75c482c5e7f0
Timestamp: 1765580179 Timestamp [UCT]: 2025-12-12 22:56:19 Age [y:d:h:m:s]: 00:027:18:27:27
Block: 1432302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19890 RingCT/type: yes/0
Extra: 0103ef6bf795544a4a164f9837e5c8a2e4f1722b9f273787335cef75c482c5e7f002110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e885ba6c04de58b74460c68df70e32600cf3f4c8e6263516ebc68a896a825140 0.600000000000 1921081 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": 1432312, "vin": [ { "gen": { "height": 1432302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e885ba6c04de58b74460c68df70e32600cf3f4c8e6263516ebc68a896a825140" } } ], "extra": [ 1, 3, 239, 107, 247, 149, 84, 74, 74, 22, 79, 152, 55, 229, 200, 162, 228, 241, 114, 43, 159, 39, 55, 135, 51, 92, 239, 117, 196, 130, 197, 231, 240, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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