Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eef3c425609644a5ecb20ae33c08fea82b74c052fb9513eb605e6bcbc5b31a2

Tx prefix hash: a41dade792f87d6b05ac63c4e9d64d7e6dca3ba5b702d14d2a21f32a81a9d2ad
Tx public key: 80947afee91c4773a159c026709877f13b5a8248817ee9cff7862d77202fd309
Timestamp: 1639498386 Timestamp [UCT]: 2021-12-14 16:13:06 Age [y:d:h:m:s]: 03:090:23:30:01
Block: 395443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 843777 RingCT/type: yes/0
Extra: 0180947afee91c4773a159c026709877f13b5a8248817ee9cff7862d77202fd309021100000001408d5ef5000000000000000000

1 output(s) for total of 30.042845198000 dcy

stealth address amount amount idx
00: 07e1b63a2f0eb80c83b099adecded103cf48299b6306f3f7ab69ef4bd0971aec 30.042845198000 793362 of 0

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": 395453, "vin": [ { "gen": { "height": 395443 } } ], "vout": [ { "amount": 30042845198, "target": { "key": "07e1b63a2f0eb80c83b099adecded103cf48299b6306f3f7ab69ef4bd0971aec" } } ], "extra": [ 1, 128, 148, 122, 254, 233, 28, 71, 115, 161, 89, 192, 38, 112, 152, 119, 241, 59, 90, 130, 72, 129, 126, 233, 207, 247, 134, 45, 119, 32, 47, 211, 9, 2, 17, 0, 0, 0, 1, 64, 141, 94, 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