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: d6ab168a501a47153187100beb8e59f683b9ed12c3995b2986012100b9b272d5
Tx prefix hash: 164b6ececfa42afd24ebe214c8591205c9cce392529a948ede494c40bfd0e791
Tx public key: a00de0b01718e2959262bf134dc78c4eea2fb12fbf40f48011f847b19b30c618
| Timestamp: 1780974777 | Timestamp [UTC]: 2026-06-09 03:12:57 | Age [y:d:h:m:s]: 00:000:09:24:48 |
| Block: 7921 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 659 | RingCT/type: yes/0 |
| Extra: 01a00de0b01718e2959262bf134dc78c4eea2fb12fbf40f48011f847b19b30c618020900000004e49593ff00 | ||
1 output(s) for total of 34.656863737931 HMNY
| stealth address | amount | amount idx | tag |
| 00: c69693f7ee43a2692eda7c504c1fdf272e3f8f83f4f1808c6ad46fb1837f9440 | 34.656863737931 | 9823 of 0 | <c8> |
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": 7981,
"vin": [ {
"gen": {
"height": 7921
}
}
],
"vout": [ {
"amount": 34656863737931,
"target": {
"tagged_key": {
"key": "c69693f7ee43a2692eda7c504c1fdf272e3f8f83f4f1808c6ad46fb1837f9440",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 160, 13, 224, 176, 23, 24, 226, 149, 146, 98, 191, 19, 77, 199, 140, 78, 234, 47, 177, 47, 191, 64, 244, 128, 17, 248, 71, 177, 155, 48, 198, 24, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}