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: b78efbbcf02c03012360d6a6d1ec7dee530784a76684b0a5e9ccc69eedff456c
Tx prefix hash: b8bdfbca18e5099cf732f9bf2690588b57c887cc226630b7450ba3b92cb6eb14
Tx public key: 9c23d8305120bf371acfb6221aa2501b000d10f425ba2a17bbeaefb82e1f65fb
| Timestamp: 1780822509 | Timestamp [UTC]: 2026-06-07 08:55:09 | Age [y:d:h:m:s]: 00:001:14:23:44 |
| Block: 7204 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 682 | RingCT/type: yes/0 |
| Extra: 019c23d8305120bf371acfb6221aa2501b000d10f425ba2a17bbeaefb82e1f65fb020900000001e49593ff00 | ||
1 output(s) for total of 34.704291857819 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5da1e24d05d882a7eace817674ed8cbd17fe85828de72b6850b0405fa02818e8 | 34.704291857819 | 8872 of 0 | <e9> |
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": 7264,
"vin": [ {
"gen": {
"height": 7204
}
}
],
"vout": [ {
"amount": 34704291857819,
"target": {
"tagged_key": {
"key": "5da1e24d05d882a7eace817674ed8cbd17fe85828de72b6850b0405fa02818e8",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 156, 35, 216, 48, 81, 32, 191, 55, 26, 207, 182, 34, 26, 162, 80, 27, 0, 13, 16, 244, 37, 186, 42, 23, 187, 234, 239, 184, 46, 31, 101, 251, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}