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: 0ab13225f18e6895bce1d32b54a1046f7b9246cb0e627faec720d00cceb42129
Tx prefix hash: a9837bfde04386f173647590f96d945d2a8ed516eef9bb994e3962d10c0261b0
Tx public key: 6f0ae73e76b29f16534da0ae0bb54c30bfefc669ef5e5712a8a265b4b8c3ed8b
| Timestamp: 1780685443 | Timestamp [UTC]: 2026-06-05 18:50:43 | Age [y:d:h:m:s]: 00:003:06:45:14 |
| Block: 5388 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2498 | RingCT/type: yes/0 |
| Extra: 016f0ae73e76b29f16534da0ae0bb54c30bfefc669ef5e5712a8a265b4b8c3ed8b020900000001e49593ff00 | ||
1 output(s) for total of 34.824707217791 HMNY
| stealth address | amount | amount idx | tag |
| 00: eab6b9c65a52a1dda5330f8f7576021c870c14063190f945f4a9ab40e6555e2b | 34.824707217791 | 6825 of 0 | <9d> |
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": 5448,
"vin": [ {
"gen": {
"height": 5388
}
}
],
"vout": [ {
"amount": 34824707217791,
"target": {
"tagged_key": {
"key": "eab6b9c65a52a1dda5330f8f7576021c870c14063190f945f4a9ab40e6555e2b",
"view_tag": "9d"
}
}
}
],
"extra": [ 1, 111, 10, 231, 62, 118, 178, 159, 22, 83, 77, 160, 174, 11, 181, 76, 48, 191, 239, 198, 105, 239, 94, 87, 18, 168, 162, 101, 180, 184, 195, 237, 139, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}