Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d0a709c35eab24cca3893cf17a902b3b7b3db4064c83b1f60fab8a752ec19ce

Tx prefix hash: 7ccf92fcb0a37e8a83ae62ad20d1062070f21db6514078a5fde7937ea92bb36d
Tx public key: ce026edf3f047772fdc90bca7099f995aa8de2c5a65bad805f7e821f2538882f
Timestamp: 1657265030 Timestamp [UCT]: 2022-07-08 07:23:50 Age [y:d:h:m:s]: 02:179:09:20:40
Block: 539161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649552 RingCT/type: yes/0
Extra: 01ce026edf3f047772fdc90bca7099f995aa8de2c5a65bad805f7e821f2538882f021100000009bf7ee4e7000000000000000000

1 output(s) for total of 10.035428910000 dcy

stealth address amount amount idx
00: e3b92389502d300a7f61a3c40538e1019b634102aa821747463aeb13d59fea96 10.035428910000 969236 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": 539171, "vin": [ { "gen": { "height": 539161 } } ], "vout": [ { "amount": 10035428910, "target": { "key": "e3b92389502d300a7f61a3c40538e1019b634102aa821747463aeb13d59fea96" } } ], "extra": [ 1, 206, 2, 110, 223, 63, 4, 119, 114, 253, 201, 11, 202, 112, 153, 249, 149, 170, 141, 226, 197, 166, 91, 173, 128, 95, 126, 130, 31, 37, 56, 136, 47, 2, 17, 0, 0, 0, 9, 191, 126, 228, 231, 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