Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d79eaa97647bc20a8d0a217f0ec1ba86963a337a7363157c4701c28a6d3b4bac

Tx prefix hash: fe82c6b7b68994d39eb406ee7bb01aa9939070a58e03cb66eb964791745e7b67
Tx public key: ee145d1261d91e8c1ef0cbd6b6a521cf3de59f33446490b254fd970d73b4c464
Timestamp: 1710636353 Timestamp [UCT]: 2024-03-17 00:45:53 Age [y:d:h:m:s]: 01:038:16:09:52
Block: 979948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288616 RingCT/type: yes/0
Extra: 01ee145d1261d91e8c1ef0cbd6b6a521cf3de59f33446490b254fd970d73b4c46402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e77a58c323ac0a8400b3682085618d34d06ca4396d32517b1a0e662b1d2bd2f7 0.600000000000 1440003 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": 979958, "vin": [ { "gen": { "height": 979948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e77a58c323ac0a8400b3682085618d34d06ca4396d32517b1a0e662b1d2bd2f7" } } ], "extra": [ 1, 238, 20, 93, 18, 97, 217, 30, 140, 30, 240, 203, 214, 182, 165, 33, 207, 61, 229, 159, 51, 68, 100, 144, 178, 84, 253, 151, 13, 115, 180, 196, 100, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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