Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd2a43db6173fc93454688f61927f9bf9fef9a0fb8efabe9360d89a0f51f1ed1

Tx prefix hash: e8afeda35788d0f3d727a257ee2f6736641e927ae12e5b656d9ef436127abd6e
Tx public key: 558fdfdbb4dce5c262fd9a576ac5c462e7227e8333170590d7b64ab20f7efa13
Timestamp: 1637389789 Timestamp [UCT]: 2021-11-20 06:29:49 Age [y:d:h:m:s]: 03:059:08:32:18
Block: 378113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 821273 RingCT/type: yes/0
Extra: 01558fdfdbb4dce5c262fd9a576ac5c462e7227e8333170590d7b64ab20f7efa130211000000081cab2639000000000000000000

1 output(s) for total of 34.289018375000 dcy

stealth address amount amount idx
00: b2f1214a1e20d941a0ae0a292f8b303cf7af4e13b6d6c2c87605d1ceb00bff91 34.289018375000 764682 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": 378123, "vin": [ { "gen": { "height": 378113 } } ], "vout": [ { "amount": 34289018375, "target": { "key": "b2f1214a1e20d941a0ae0a292f8b303cf7af4e13b6d6c2c87605d1ceb00bff91" } } ], "extra": [ 1, 85, 143, 223, 219, 180, 220, 229, 194, 98, 253, 154, 87, 106, 197, 196, 98, 231, 34, 126, 131, 51, 23, 5, 144, 215, 182, 74, 178, 15, 126, 250, 19, 2, 17, 0, 0, 0, 8, 28, 171, 38, 57, 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