Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 075b08380265702f66f4e5189228f52a4f9c2892ff3fc8a3a0f4a37ebc859098

Tx prefix hash: 302c39011c7b6d80f17e37e081ac392795c1c0c474929a26f244cf73aaa2dcd4
Tx public key: d6277d1bd33bb900846d3f23071132e68e7c88678f1a7d5cce874720d7d1bc91
Timestamp: 1717660125 Timestamp [UCT]: 2024-06-06 07:48:45 Age [y:d:h:m:s]: 00:349:00:03:26
Block: 1038163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249452 RingCT/type: yes/0
Extra: 01d6277d1bd33bb900846d3f23071132e68e7c88678f1a7d5cce874720d7d1bc910211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 353b0f4fcffaccfadbb6e76b3e0b8c8511aa1b5199f34d04c36cc14f0667a654 0.600000000000 1506724 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": 1038173, "vin": [ { "gen": { "height": 1038163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "353b0f4fcffaccfadbb6e76b3e0b8c8511aa1b5199f34d04c36cc14f0667a654" } } ], "extra": [ 1, 214, 39, 125, 27, 211, 59, 185, 0, 132, 109, 63, 35, 7, 17, 50, 230, 142, 124, 136, 103, 143, 26, 125, 92, 206, 135, 71, 32, 215, 209, 188, 145, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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