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: 376083a41ca18063441ee61be571ee8124da51b678580a4f317fb6b6d201b331
Tx prefix hash: b070a45d45c4fb57c6a471e51f89c8f91ab59ec07df81a0138f1566f76e06954
Tx public key: 2c0e3488298d1de687e57d14c131d70341297d3fefa8f0af9be1a3850005ad87
| Timestamp: 1779940489 | Timestamp [UTC]: 2026-05-28 03:54:49 | Age [y:d:h:m:s]: 00:011:21:41:08 |
| Block: 3486 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4400 | RingCT/type: yes/0 |
| Extra: 012c0e3488298d1de687e57d14c131d70341297d3fefa8f0af9be1a3850005ad8702090000000126697be300 | ||
1 output(s) for total of 34.951273051346 HMNY
| stealth address | amount | amount idx | tag |
| 00: 287e62fcc48526152e709a726582df7e39042ef8c71a1e88b8b8dce5e75f8fd5 | 34.951273051346 | 4205 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": 3546,
"vin": [ {
"gen": {
"height": 3486
}
}
],
"vout": [ {
"amount": 34951273051346,
"target": {
"tagged_key": {
"key": "287e62fcc48526152e709a726582df7e39042ef8c71a1e88b8b8dce5e75f8fd5",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 44, 14, 52, 136, 41, 141, 29, 230, 135, 229, 125, 20, 193, 49, 215, 3, 65, 41, 125, 63, 239, 168, 240, 175, 155, 225, 163, 133, 0, 5, 173, 135, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}