Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39cf3c8056d9e981e4c7359733120d3e8c5b7e975ffe4d5ed8b2858f79815fb3

Tx prefix hash: 186f8b095970756cddd607444199b9cba82c7ec34f9ccab421da6b35c34eba6c
Tx public key: a853782835bee34ad149e9f48641c34162fde00e9b5ba394318d1785aa931646
Timestamp: 1574999436 Timestamp [UCT]: 2019-11-29 03:50:36 Age [y:d:h:m:s]: 05:338:11:00:24
Block: 19430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1382567 RingCT/type: yes/0
Extra: 01a853782835bee34ad149e9f48641c34162fde00e9b5ba394318d1785aa93164602110000002cad433a0b000000000000000000

1 output(s) for total of 529.201689337000 dcy

stealth address amount amount idx
00: bbf85fa4f027dfe2d54c242575dcbb4e7b2783fae4dc12caad48e62f6bbc4081 529.201689337000 30545 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": 19440, "vin": [ { "gen": { "height": 19430 } } ], "vout": [ { "amount": 529201689337, "target": { "key": "bbf85fa4f027dfe2d54c242575dcbb4e7b2783fae4dc12caad48e62f6bbc4081" } } ], "extra": [ 1, 168, 83, 120, 40, 53, 190, 227, 74, 209, 73, 233, 244, 134, 65, 195, 65, 98, 253, 224, 14, 155, 91, 163, 148, 49, 141, 23, 133, 170, 147, 22, 70, 2, 17, 0, 0, 0, 44, 173, 67, 58, 11, 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