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: edc9f22f5074945331b45fdef1d979711ba83202852ab5ab2283ce74c8784c88
Tx prefix hash: 608541b84ea62f5bd61e9d9370dc4ebde4a31e3845f8dc0594f27eef532b8dfc
Tx public key: b093015c5b8d522cc453b1fb2e5848ca237df2a49754d51f1861860dc6fee39a
| Timestamp: 1779959058 | Timestamp [UTC]: 2026-05-28 09:04:18 | Age [y:d:h:m:s]: 00:011:18:46:40 |
| Block: 3733 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4219 | RingCT/type: yes/0 |
| Extra: 01b093015c5b8d522cc453b1fb2e5848ca237df2a49754d51f1861860dc6fee39a02090000000826697be300 | ||
1 output(s) for total of 34.934810840820 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8ed4a2108d533160ce9c633920b0df8b7ef19fc8d9060b997ef625a6f36d78f8 | 34.934810840820 | 4522 of 0 | <8b> |
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": 3793,
"vin": [ {
"gen": {
"height": 3733
}
}
],
"vout": [ {
"amount": 34934810840820,
"target": {
"tagged_key": {
"key": "8ed4a2108d533160ce9c633920b0df8b7ef19fc8d9060b997ef625a6f36d78f8",
"view_tag": "8b"
}
}
}
],
"extra": [ 1, 176, 147, 1, 92, 91, 141, 82, 44, 196, 83, 177, 251, 46, 88, 72, 202, 35, 125, 242, 164, 151, 84, 213, 31, 24, 97, 134, 13, 198, 254, 227, 154, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}