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: 52f1414e4e396884a433d3874a7a736804cc9998c64b7c69252fa025d0fbef63
Tx prefix hash: 82a5bbd0b8b557052e79ae00ceb24fbe03fba2a769a39031e2cfafabda1f03dd
Tx public key: 8607f6080e49570ea77aa2631d6459c49a396347b5d1e64650c747a59359fbf8
| Timestamp: 1779769464 | Timestamp [UTC]: 2026-05-26 04:24:24 | Age [y:d:h:m:s]: 00:018:06:37:52 |
| Block: 1996 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6749 | RingCT/type: yes/0 |
| Extra: 018607f6080e49570ea77aa2631d6459c49a396347b5d1e64650c747a59359fbf802090000000226697be300 | ||
1 output(s) for total of 35.050744176891 HMNY
| stealth address | amount | amount idx | tag |
| 00: 44e6f74385b85bbf1ed01e76508c7afe0d5c39329164b738f04d201ebfc575b2 | 35.050744176891 | 2276 of 0 | <f4> |
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": 2056,
"vin": [ {
"gen": {
"height": 1996
}
}
],
"vout": [ {
"amount": 35050744176891,
"target": {
"tagged_key": {
"key": "44e6f74385b85bbf1ed01e76508c7afe0d5c39329164b738f04d201ebfc575b2",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 134, 7, 246, 8, 14, 73, 87, 14, 167, 122, 162, 99, 29, 100, 89, 196, 154, 57, 99, 71, 181, 209, 230, 70, 80, 199, 71, 165, 147, 89, 251, 248, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}