Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69515e1d5866c0f3736307eb4c72e7e1f42a477b3d876c66e8cd58b1d84db63c

Tx prefix hash: d85e66ae3d6ff9638a27dacc4e228132e29e63377a52d6a1bd8530524a18e6e5
Tx public key: c4835cf7b5c926e1aa136209ca9fb1357f1e479e833278c0fa25ea96c4393c6c
Timestamp: 1737734421 Timestamp [UCT]: 2025-01-24 16:00:21 Age [y:d:h:m:s]: 00:144:10:01:10
Block: 1204377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102962 RingCT/type: yes/0
Extra: 01c4835cf7b5c926e1aa136209ca9fb1357f1e479e833278c0fa25ea96c4393c6c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f879ab0ea9f0583fd4dce76c0d42413a3079a4c9aa08bc7202c88a28c8c9258 0.600000000000 1691062 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": 1204387, "vin": [ { "gen": { "height": 1204377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f879ab0ea9f0583fd4dce76c0d42413a3079a4c9aa08bc7202c88a28c8c9258" } } ], "extra": [ 1, 196, 131, 92, 247, 181, 201, 38, 225, 170, 19, 98, 9, 202, 159, 177, 53, 127, 30, 71, 158, 131, 50, 120, 192, 250, 37, 234, 150, 196, 57, 60, 108, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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