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: 074c0b2e327c51a6c6004c13435143375803efcbafe42ad43425197f90d2382d
Tx prefix hash: d4a7c69cc00c64991f10b882a9e5e15ea71f4e3254467fd083367fd5d0b7bd31
Tx public key: f8b54c9b4e26b5c3c977cd0e3546d53debfbd276dea446d3321f8924bcffd6a4
| Timestamp: 1780069295 | Timestamp [UTC]: 2026-05-29 15:41:35 | Age [y:d:h:m:s]: 00:010:11:08:13 |
| Block: 4625 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3284 | RingCT/type: yes/0 |
| Extra: 01f8b54c9b4e26b5c3c977cd0e3546d53debfbd276dea446d3321f8924bcffd6a402090000000426697be300 | ||
1 output(s) for total of 34.875424802461 HMNY
| stealth address | amount | amount idx | tag |
| 00: d5f4ed50b942d6ba446c4d7e98eacc6961ebd21534c9fcebadafa5b7529c6c93 | 34.875424802461 | 5808 of 0 | <c6> |
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": 4685,
"vin": [ {
"gen": {
"height": 4625
}
}
],
"vout": [ {
"amount": 34875424802461,
"target": {
"tagged_key": {
"key": "d5f4ed50b942d6ba446c4d7e98eacc6961ebd21534c9fcebadafa5b7529c6c93",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 248, 181, 76, 155, 78, 38, 181, 195, 201, 119, 205, 14, 53, 70, 213, 61, 235, 251, 210, 118, 222, 164, 70, 211, 50, 31, 137, 36, 188, 255, 214, 164, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}