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: 363c0d744a73e24c63227ef8346c0ec987fa52d49d3fa016ae54d4736522278f
Tx prefix hash: c6ce0ca7c0ca70a9a9e757d4df64695d640d2ca78461e3574874886bdf530c57
Tx public key: 2f30c46944dfddff96fe67eb1123dc270bbd1e2298ad95ba8b274d6139f0bcab
| Timestamp: 1780323072 | Timestamp [UTC]: 2026-06-01 14:11:12 | Age [y:d:h:m:s]: 00:007:13:27:38 |
| Block: 5048 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2901 | RingCT/type: yes/0 |
| Extra: 012f30c46944dfddff96fe67eb1123dc270bbd1e2298ad95ba8b274d6139f0bcab02090000005c26697be300 | ||
1 output(s) for total of 34.847298335315 HMNY
| stealth address | amount | amount idx | tag |
| 00: a58ec6b358e192e7444b75f9056a0f6bbff85a001357d8e2f1c37d67c8cf6d98 | 34.847298335315 | 6423 of 0 | <a9> |
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": 5108,
"vin": [ {
"gen": {
"height": 5048
}
}
],
"vout": [ {
"amount": 34847298335315,
"target": {
"tagged_key": {
"key": "a58ec6b358e192e7444b75f9056a0f6bbff85a001357d8e2f1c37d67c8cf6d98",
"view_tag": "a9"
}
}
}
],
"extra": [ 1, 47, 48, 196, 105, 68, 223, 221, 255, 150, 254, 103, 235, 17, 35, 220, 39, 11, 189, 30, 34, 152, 173, 149, 186, 139, 39, 77, 97, 57, 240, 188, 171, 2, 9, 0, 0, 0, 92, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}