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: 2bbfcc9bccf4a4384b70fe6badb49388f8f341d8482e23e266d8a930710eec25
Tx prefix hash: 3668513af4ef01bf3d91621621fdbe9a5f4fe67800b171f6cb2f9b6f3d14b4ef
Tx public key: 42c2c05cbc8537b266423759761643b76add4a956d9b8d580fd6f5998abf6ded
| Timestamp: 1779790285 | Timestamp [UTC]: 2026-05-26 10:11:25 | Age [y:d:h:m:s]: 00:021:22:10:54 |
| Block: 2215 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6530 | RingCT/type: yes/0 |
| Extra: 0142c2c05cbc8537b266423759761643b76add4a956d9b8d580fd6f5998abf6ded02090000000426697be300 | ||
1 output(s) for total of 35.036106196767 HMNY
| stealth address | amount | amount idx | tag |
| 00: e7042a18e3c15dc3d6ec9950b313761599c8aa490ddfea362d2af4feb3253930 | 35.036106196767 | 2565 of 0 | <18> |
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": 2275,
"vin": [ {
"gen": {
"height": 2215
}
}
],
"vout": [ {
"amount": 35036106196767,
"target": {
"tagged_key": {
"key": "e7042a18e3c15dc3d6ec9950b313761599c8aa490ddfea362d2af4feb3253930",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 66, 194, 192, 92, 188, 133, 55, 178, 102, 66, 55, 89, 118, 22, 67, 183, 106, 221, 74, 149, 109, 155, 141, 88, 15, 214, 245, 153, 138, 191, 109, 237, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}