For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: ee0aa182f656763e45cdbdcd7e53e1cef8093b9fc29a78d1e2ebca8e45de4370
Tx prefix hash: 92d6dc64c426f77a0a520fc2872ecb990d62162a87273d80eb677bc363419b01
Tx public key: d062258e33986b15673bf634a4a442b640f5b5cb836d030af5db23e772579080
| Timestamp: 1780979790 | Timestamp [UTC]: 2026-06-09 04:36:30 | Age [y:d:h:m:s]: 00:000:07:56:57 |
| Block: 8008 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 562 | RingCT/type: yes/0 |
| Extra: 01d062258e33986b15673bf634a4a442b640f5b5cb836d030af5db23e772579080020900000001e49593ff00 | ||
1 output(s) for total of 34.651113272789 HMNY
| stealth address | amount | amount idx | tag |
| 00: 550c052612eb2d9377268e4af83f98c5556150a3f41579770adac8374c6f8810 | 34.651113272789 | 9928 of 0 | <d1> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 8068,
"vin": [ {
"gen": {
"height": 8008
}
}
],
"vout": [ {
"amount": 34651113272789,
"target": {
"tagged_key": {
"key": "550c052612eb2d9377268e4af83f98c5556150a3f41579770adac8374c6f8810",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 208, 98, 37, 142, 51, 152, 107, 21, 103, 59, 246, 52, 164, 164, 66, 182, 64, 245, 181, 203, 131, 109, 3, 10, 245, 219, 35, 231, 114, 87, 144, 128, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}