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: f9094fabb25ea6ee3401842fa7867095e49082830e3cfeac2daab4b97d86598c
Tx prefix hash: c88fc43e276e7f8200053cbed03569b0bbf3440254651fa9fe9033d6c5ee7f45
Tx public key: 1fe8f05cb8908a7a8a4855746afa44f8e463928d3e3d672c5620acf5f4d4eb13
| Timestamp: 1780896682 | Timestamp [UTC]: 2026-06-08 05:31:22 | Age [y:d:h:m:s]: 00:000:20:04:35 |
| Block: 7770 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 116 | RingCT/type: yes/0 |
| Extra: 011fe8f05cb8908a7a8a4855746afa44f8e463928d3e3d672c5620acf5f4d4eb130209000000014a728a4c00 | ||
1 output(s) for total of 34.666846695949 HMNY
| stealth address | amount | amount idx | tag |
| 00: b54c3dd08f02b3e83e358a3a008aaaa148d9518dcc65eaa512a06fca4ca89038 | 34.666846695949 | 9628 of 0 | <b9> |
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": 7830,
"vin": [ {
"gen": {
"height": 7770
}
}
],
"vout": [ {
"amount": 34666846695949,
"target": {
"tagged_key": {
"key": "b54c3dd08f02b3e83e358a3a008aaaa148d9518dcc65eaa512a06fca4ca89038",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 31, 232, 240, 92, 184, 144, 138, 122, 138, 72, 85, 116, 106, 250, 68, 248, 228, 99, 146, 141, 62, 61, 103, 44, 86, 32, 172, 245, 244, 212, 235, 19, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}