Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17d418e1693c819d399ff4c53fad10d332263385c6c9ebaaeeaf99395770b7f

Tx prefix hash: c6d59d247fa0cc348aa2a40833d2dc52a5e8eb084ae5c364f6ce5e4d278ed420
Tx public key: d92158d2de869c6e17524ec82e6621411de50b94ca797acfd1d84ef87e7f8024
Timestamp: 1749723089 Timestamp [UCT]: 2025-06-12 10:11:29 Age [y:d:h:m:s]: 00:155:10:28:54
Block: 1303382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108811 RingCT/type: yes/0
Extra: 01d92158d2de869c6e17524ec82e6621411de50b94ca797acfd1d84ef87e7f8024021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfd670150fe4e7a7cc6dc7eae862323e21c50d1c12bb84c3d0225af53541ce2f 0.600000000000 1790961 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": 1303392, "vin": [ { "gen": { "height": 1303382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfd670150fe4e7a7cc6dc7eae862323e21c50d1c12bb84c3d0225af53541ce2f" } } ], "extra": [ 1, 217, 33, 88, 210, 222, 134, 156, 110, 23, 82, 78, 200, 46, 102, 33, 65, 29, 229, 11, 148, 202, 121, 122, 207, 209, 216, 78, 248, 126, 127, 128, 36, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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