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: 2ce3d9413f9ea64b63908ca6f34d06fa6851b02c0fb18ea9ebf7377e2fdda25b
Tx prefix hash: 4f4145ac3a03ea9ac4d70fb45f7e53de7dc7565432ab66173ee8f31e37bccfc5
Tx public key: 3ecab1b31db5ed49f39f45093e6c74a3f09f2b9ba9b69d6d8ca9500e340b7f4c
| Timestamp: 1779914761 | Timestamp [UTC]: 2026-05-27 20:46:01 | Age [y:d:h:m:s]: 00:012:05:54:35 |
| Block: 3285 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4611 | RingCT/type: yes/0 |
| Extra: 013ecab1b31db5ed49f39f45093e6c74a3f09f2b9ba9b69d6d8ca9500e340b7f4c02090000000226697be300 | ||
1 output(s) for total of 34.964675149829 HMNY
| stealth address | amount | amount idx | tag |
| 00: b8afc52089a13789cecd539d5b83fecb069afe755f341b520a68a35321a15c18 | 34.964675149829 | 3945 of 0 | <7c> |
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": 3345,
"vin": [ {
"gen": {
"height": 3285
}
}
],
"vout": [ {
"amount": 34964675149829,
"target": {
"tagged_key": {
"key": "b8afc52089a13789cecd539d5b83fecb069afe755f341b520a68a35321a15c18",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 62, 202, 177, 179, 29, 181, 237, 73, 243, 159, 69, 9, 62, 108, 116, 163, 240, 159, 43, 155, 169, 182, 157, 109, 140, 169, 80, 14, 52, 11, 127, 76, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}