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: e172230800e884c9c6283f40f5d1403ea2436cac092f2c8d8139ea6472ffb1b8
Tx prefix hash: 7f00c95097d07c2edd4a79edf7b8e2fefb16b4d5d4edfc2a161c151c119df56e
Tx public key: 13d6f2e30180400f4bde82a069b775d20ccd38e50edf53459c61bbf8192299c5
| Timestamp: 1780802760 | Timestamp [UTC]: 2026-06-07 03:26:00 | Age [y:d:h:m:s]: 00:010:05:03:12 |
| Block: 6872 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1873 | RingCT/type: yes/0 |
| Extra: 0113d6f2e30180400f4bde82a069b775d20ccd38e50edf53459c61bbf8192299c5020900000002e49593ff00 | ||
1 output(s) for total of 34.726274975305 HMNY
| stealth address | amount | amount idx | tag |
| 00: 91aa29963c85bbc9b6af7bfb130b48d8394c3f656791a2efc63c9caf10bf27f4 | 34.726274975305 | 8482 of 0 | <c0> |
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": 6932,
"vin": [ {
"gen": {
"height": 6872
}
}
],
"vout": [ {
"amount": 34726274975305,
"target": {
"tagged_key": {
"key": "91aa29963c85bbc9b6af7bfb130b48d8394c3f656791a2efc63c9caf10bf27f4",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 19, 214, 242, 227, 1, 128, 64, 15, 75, 222, 130, 160, 105, 183, 117, 210, 12, 205, 56, 229, 14, 223, 83, 69, 156, 97, 187, 248, 25, 34, 153, 197, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}