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: b114551910d3af1d5bc27a20f93a634de9605463df07628d7fe4062dc4826420
Tx prefix hash: f54d8c07bb38bc68e68f3e6fd6b408259fd3cdbb98a0cd41ca18ddfcd387bf5c
Tx public key: f63789215f13c9e08a08b7b04ec97788daebfdc352c0cfe521d6667aada3e5a0
| Timestamp: 1780069929 | Timestamp [UTC]: 2026-05-29 15:52:09 | Age [y:d:h:m:s]: 00:010:08:54:38 |
| Block: 4632 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3254 | RingCT/type: yes/0 |
| Extra: 01f63789215f13c9e08a08b7b04ec97788daebfdc352c0cfe521d6667aada3e5a002090000000426697be300 | ||
1 output(s) for total of 34.874959167968 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4fab380bec6757ac83c5a7107ea79abfbdbc6f66c01f66d229bb5445df568ca6 | 34.874959167968 | 5817 of 0 | <f9> |
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": 4692,
"vin": [ {
"gen": {
"height": 4632
}
}
],
"vout": [ {
"amount": 34874959167968,
"target": {
"tagged_key": {
"key": "4fab380bec6757ac83c5a7107ea79abfbdbc6f66c01f66d229bb5445df568ca6",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 246, 55, 137, 33, 95, 19, 201, 224, 138, 8, 183, 176, 78, 201, 119, 136, 218, 235, 253, 195, 82, 192, 207, 229, 33, 214, 102, 122, 173, 163, 229, 160, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}