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: 544ef4073a803036d4dcba3217c0f1544017c21d44ee4f6fee73ef146b27153e
Tx prefix hash: 8da24940571e9d1c9948098b1831324f1269ce66f860867e09e473b3c20ac9e8
Tx public key: f8c2c0659fa4f8fbc13fe99f8e07974018fb6e5509d6cb8d4e3bb868f4873f8d
| Timestamp: 1780696047 | Timestamp [UTC]: 2026-06-05 21:47:27 | Age [y:d:h:m:s]: 00:002:23:24:40 |
| Block: 5982 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1904 | RingCT/type: yes/0 |
| Extra: 01f8c2c0659fa4f8fbc13fe99f8e07974018fb6e5509d6cb8d4e3bb868f4873f8d020900000001e49593ff00 | ||
1 output(s) for total of 34.785274344963 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6835815418497107631656f70eb91f8e367b17e73f2d7f8237364b5e616e458b | 34.785274344963 | 7447 of 0 | <af> |
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": 6042,
"vin": [ {
"gen": {
"height": 5982
}
}
],
"vout": [ {
"amount": 34785274344963,
"target": {
"tagged_key": {
"key": "6835815418497107631656f70eb91f8e367b17e73f2d7f8237364b5e616e458b",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 248, 194, 192, 101, 159, 164, 248, 251, 193, 63, 233, 159, 142, 7, 151, 64, 24, 251, 110, 85, 9, 214, 203, 141, 78, 59, 184, 104, 244, 135, 63, 141, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}