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: c37f8670030da64d3fc10b7bd4dfebb219c0f7a92bc079c55ceb8a1dc2b10f65
Tx prefix hash: 8e08eb698171e92f28a49451627cc42506f4feafb0555f86b505a77e42f331ae
Tx public key: 48557b1aeb667456a840f5108d0d5e0dd8e53292cf9d2d2fee7f14b309dd2027
| Timestamp: 1780823031 | Timestamp [UTC]: 2026-06-07 09:03:51 | Age [y:d:h:m:s]: 00:009:22:57:54 |
| Block: 7210 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1535 | RingCT/type: yes/0 |
| Extra: 0148557b1aeb667456a840f5108d0d5e0dd8e53292cf9d2d2fee7f14b309dd2027020900000001e49593ff00 | ||
1 output(s) for total of 34.703894700611 HMNY
| stealth address | amount | amount idx | tag |
| 00: f880a70295355cf7011591f2e5e7fc216f5a56c5da96ca79ce179a0b0ffc684c | 34.703894700611 | 8880 of 0 | <5f> |
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": 7270,
"vin": [ {
"gen": {
"height": 7210
}
}
],
"vout": [ {
"amount": 34703894700611,
"target": {
"tagged_key": {
"key": "f880a70295355cf7011591f2e5e7fc216f5a56c5da96ca79ce179a0b0ffc684c",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 72, 85, 123, 26, 235, 102, 116, 86, 168, 64, 245, 16, 141, 13, 94, 13, 216, 229, 50, 146, 207, 157, 45, 47, 238, 127, 20, 179, 9, 221, 32, 39, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}