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: 9948e14cfd7b41ddb29a362452a7267b9cb94d1fe71f9ad9ee16dec4ac947c8a
Tx prefix hash: 19e0b78f5643038ea721bb4b699eec7b0df595b5cec9e3ea098b606c4ebc1fcc
Tx public key: 5e68bae82a46dffe34ff8e34b9727b01b7cdeffc68d6ecafd73ae14af189ef74
| Timestamp: 1781001646 | Timestamp [UTC]: 2026-06-09 10:40:46 | Age [y:d:h:m:s]: 00:007:21:55:28 |
| Block: 8461 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 284 | RingCT/type: yes/0 |
| Extra: 015e68bae82a46dffe34ff8e34b9727b01b7cdeffc68d6ecafd73ae14af189ef74020900000001e49593ff00 | ||
1 output(s) for total of 34.632619010514 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7baf5ec3ddb1c6c76d2639b0f9a204dd47bcbe27158c7e7dd9c993a50282cd92 | 34.632619010514 | 10453 of 0 | <e8> |
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": 8521,
"vin": [ {
"gen": {
"height": 8461
}
}
],
"vout": [ {
"amount": 34632619010514,
"target": {
"tagged_key": {
"key": "7baf5ec3ddb1c6c76d2639b0f9a204dd47bcbe27158c7e7dd9c993a50282cd92",
"view_tag": "e8"
}
}
}
],
"extra": [ 1, 94, 104, 186, 232, 42, 70, 223, 254, 52, 255, 142, 52, 185, 114, 123, 1, 183, 205, 239, 252, 104, 214, 236, 175, 215, 58, 225, 74, 241, 137, 239, 116, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}