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: c7f5b67304ef58815c013e2976e2c4efa551180ba151c2a073ec9b3e1aa925ae
Tx prefix hash: b4b2d56f1f702416a90774e3f75bf9e052002f1add79febcffa9f33cbe78934d
Tx public key: af0a59a026a3808d016ab8aa520d4cc3d37051e96339bdc1d7db6099375bdeec
| Timestamp: 1780802031 | Timestamp [UTC]: 2026-06-07 03:13:51 | Age [y:d:h:m:s]: 00:001:21:32:56 |
| Block: 6855 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1031 | RingCT/type: yes/0 |
| Extra: 01af0a59a026a3808d016ab8aa520d4cc3d37051e96339bdc1d7db6099375bdeec020900000001e49593ff00 | ||
1 output(s) for total of 34.727400991557 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84babad816110c34db2639228d4977f2ca6a0de8d7dd27f89ce289ed6aa27b16 | 34.727400991557 | 8463 of 0 | <59> |
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": 6915,
"vin": [ {
"gen": {
"height": 6855
}
}
],
"vout": [ {
"amount": 34727400991557,
"target": {
"tagged_key": {
"key": "84babad816110c34db2639228d4977f2ca6a0de8d7dd27f89ce289ed6aa27b16",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 175, 10, 89, 160, 38, 163, 128, 141, 1, 106, 184, 170, 82, 13, 76, 195, 211, 112, 81, 233, 99, 57, 189, 193, 215, 219, 96, 153, 55, 91, 222, 236, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}