Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9342286cb1bf464482205ec77a3f707413fbb4b5ad65fe9b70cf4edf4b01436c

Tx prefix hash: 15afc07f7d138934eda0d735aaf1b12c8ada69371f910e47a7ed602b2b6121f0
Tx public key: d5816d42e3e92184495546d10ef346aa5aad62f4da0926800d17ef03c576ea51
Timestamp: 1725804762 Timestamp [UCT]: 2024-09-08 14:12:42 Age [y:d:h:m:s]: 00:247:19:24:18
Block: 1105678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176976 RingCT/type: yes/0
Extra: 01d5816d42e3e92184495546d10ef346aa5aad62f4da0926800d17ef03c576ea51021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00cff5a57c2e98d7d248ace3e5b5ccd854aca71ba9c5ab31c2a35e8daac02b9f 0.600000000000 1583101 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": 1105688, "vin": [ { "gen": { "height": 1105678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00cff5a57c2e98d7d248ace3e5b5ccd854aca71ba9c5ab31c2a35e8daac02b9f" } } ], "extra": [ 1, 213, 129, 109, 66, 227, 233, 33, 132, 73, 85, 70, 209, 14, 243, 70, 170, 90, 173, 98, 244, 218, 9, 38, 128, 13, 23, 239, 3, 197, 118, 234, 81, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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