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: 3a8afe839044d532ee76689689fc6ccb9bc3ea6d8bc67c2d50919485dfd511cf
Tx prefix hash: 0aeafa40d5058094dcf10b408c04e5f42bd24ed4945b7a7a3b983899cff7a043
Tx public key: 3a8d30cdffded57d91dcf54cb7603d88bc47f48c89289f5f0e6f1087b5d335b6
| Timestamp: 1779630394 | Timestamp [UTC]: 2026-05-24 13:46:34 | Age [y:d:h:m:s]: 00:019:21:15:42 |
| Block: 869 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7876 | RingCT/type: yes/0 |
| Extra: 013a8d30cdffded57d91dcf54cb7603d88bc47f48c89289f5f0e6f1087b5d335b6020900000001ba6d17be00 | ||
1 output(s) for total of 35.126169732070 HMNY
| stealth address | amount | amount idx | tag |
| 00: e94e8dab499505e020729247fd9fbe2832f400adc48e38084f65f7a7978ed06d | 35.126169732070 | 1001 of 0 | <4f> |
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": 929,
"vin": [ {
"gen": {
"height": 869
}
}
],
"vout": [ {
"amount": 35126169732070,
"target": {
"tagged_key": {
"key": "e94e8dab499505e020729247fd9fbe2832f400adc48e38084f65f7a7978ed06d",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 58, 141, 48, 205, 255, 222, 213, 125, 145, 220, 245, 76, 183, 96, 61, 136, 188, 71, 244, 140, 137, 40, 159, 95, 14, 111, 16, 135, 181, 211, 53, 182, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}