Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1066f2fd95fcebc8e8227e748e3251f3f444efaf8c475e9987087c921519aeab

Tx prefix hash: a5db08f1e4b67b47c0a0f129b940dfe71ce73e1091565e4a344178c4f5a5b3cd
Tx public key: a3b42e4a7d737a0b348aceb5779778e04bc5c14e3fc3d413dfb331ece75145ba
Timestamp: 1764808604 Timestamp [UCT]: 2025-12-04 00:36:44 Age [y:d:h:m:s]: 00:000:14:29:42
Block: 1425909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452 RingCT/type: yes/0
Extra: 01a3b42e4a7d737a0b348aceb5779778e04bc5c14e3fc3d413dfb331ece75145ba021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 170252b097fb070376bf5b8feb91976d3e66b682d29c2b864e5bce40a1178329 0.600000000000 1914592 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": 1425919, "vin": [ { "gen": { "height": 1425909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "170252b097fb070376bf5b8feb91976d3e66b682d29c2b864e5bce40a1178329" } } ], "extra": [ 1, 163, 180, 46, 74, 125, 115, 122, 11, 52, 138, 206, 181, 119, 151, 120, 224, 75, 197, 193, 78, 63, 195, 212, 19, 223, 179, 49, 236, 231, 81, 69, 186, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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