Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a323ee80d911a4dee6f7a4531b1fca8f63ff8ad1877a72b9ae95c8ad32e3ef82

Tx prefix hash: 2137157061ca673312ee3dca3b7048b572dd55a77c957d5d06a5a261930a7891
Tx public key: 6d01f22f1410550512b5e3509fa4efcc93b6c8a9d95baeb3fe685dfb76deb1c0
Timestamp: 1708573500 Timestamp [UCT]: 2024-02-22 03:45:00 Age [y:d:h:m:s]: 00:337:19:17:15
Block: 962823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241771 RingCT/type: yes/0
Extra: 016d01f22f1410550512b5e3509fa4efcc93b6c8a9d95baeb3fe685dfb76deb1c002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f9a891cf07f8c63968a7d320494d3b247a96a3d9c12073af79c75337b42671c 0.600000000000 1422508 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": 962833, "vin": [ { "gen": { "height": 962823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f9a891cf07f8c63968a7d320494d3b247a96a3d9c12073af79c75337b42671c" } } ], "extra": [ 1, 109, 1, 242, 47, 20, 16, 85, 5, 18, 181, 227, 80, 159, 164, 239, 204, 147, 182, 200, 169, 217, 91, 174, 179, 254, 104, 93, 251, 118, 222, 177, 192, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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