Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b9613178d160bd618e6952ac7f8fcc1bd43ea04806037a54f8caf6e10af086e

Tx prefix hash: 766cefd08d4526004083f7e2498e4e72d085ea70de2e2250ef3c32342018f140
Tx public key: ab1d817e48ce4cf6334264a5c166746d3dacb94cbcba0fe1b4cfb395cd6408a1
Timestamp: 1592983840 Timestamp [UCT]: 2020-06-24 07:30:40 Age [y:d:h:m:s]: 04:340:21:21:11
Block: 110366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183597 RingCT/type: yes/0
Extra: 01ab1d817e48ce4cf6334264a5c166746d3dacb94cbcba0fe1b4cfb395cd6408a102110000000b4943cd9f000000000000000000

1 output(s) for total of 264.435574275000 dcy

stealth address amount amount idx
00: 9f156a7341070d32471f916f502c68e3bc4e504032ef22f3fa6d193cd74377c9 264.435574275000 191212 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": 110376, "vin": [ { "gen": { "height": 110366 } } ], "vout": [ { "amount": 264435574275, "target": { "key": "9f156a7341070d32471f916f502c68e3bc4e504032ef22f3fa6d193cd74377c9" } } ], "extra": [ 1, 171, 29, 129, 126, 72, 206, 76, 246, 51, 66, 100, 165, 193, 102, 116, 109, 61, 172, 185, 76, 188, 186, 15, 225, 180, 207, 179, 149, 205, 100, 8, 161, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 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