Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3fadab608cb2cf1afa089de5ce815d6d6f2a385acecd864e58d610e6ce691f

Tx prefix hash: 999b0050d810bb9a23ed2f94d8c3db2e21b335938e211c5116ace561829e6e09
Tx public key: a01f9e91d2a94b6bd68cadf73f4217eb2121ff0898cf824031fb5f74cb9c2239
Timestamp: 1719929684 Timestamp [UCT]: 2024-07-02 14:14:44 Age [y:d:h:m:s]: 00:144:20:39:55
Block: 1056975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103663 RingCT/type: yes/0
Extra: 01a01f9e91d2a94b6bd68cadf73f4217eb2121ff0898cf824031fb5f74cb9c22390211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 314d3beec53c457f622b902d3392faf2819c76258fb93c926693d42649e42cab 0.600000000000 1527404 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": 1056985, "vin": [ { "gen": { "height": 1056975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "314d3beec53c457f622b902d3392faf2819c76258fb93c926693d42649e42cab" } } ], "extra": [ 1, 160, 31, 158, 145, 210, 169, 75, 107, 214, 140, 173, 247, 63, 66, 23, 235, 33, 33, 255, 8, 152, 207, 130, 64, 49, 251, 95, 116, 203, 156, 34, 57, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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