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: 97acdbe256f6472fbdecbb75d679408f6ee1385f44eb3affe86b9bd0d2bc5e9d
Tx prefix hash: cf2062f84e56bd0628ba71f6947babfa72e0e5fd7e8993728ed3e21d4d42afd2
Tx public key: fe1426d43e9eb5bab1c5e3f54f74ef8582ee6e4d1d6e85b5167a94da8c6cfd51
| Timestamp: 1780831396 | Timestamp [UTC]: 2026-06-07 11:23:16 | Age [y:d:h:m:s]: 00:005:23:39:00 |
| Block: 7346 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1399 | RingCT/type: yes/0 |
| Extra: 01fe1426d43e9eb5bab1c5e3f54f74ef8582ee6e4d1d6e85b5167a94da8c6cfd51020900000003e49593ff00 | ||
1 output(s) for total of 34.694893689555 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1f5b3712fc3e7f726269b420826f068d78582b1ffa481aa98430bc369142a5ce | 34.694893689555 | 9044 of 0 | <f8> |
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": 7406,
"vin": [ {
"gen": {
"height": 7346
}
}
],
"vout": [ {
"amount": 34694893689555,
"target": {
"tagged_key": {
"key": "1f5b3712fc3e7f726269b420826f068d78582b1ffa481aa98430bc369142a5ce",
"view_tag": "f8"
}
}
}
],
"extra": [ 1, 254, 20, 38, 212, 62, 158, 181, 186, 177, 197, 227, 245, 79, 116, 239, 133, 130, 238, 110, 77, 29, 110, 133, 181, 22, 122, 148, 218, 140, 108, 253, 81, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}