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: d5622313a53d99b4cbfe55fdb5e724d86f77533326782c6e4d5a928ef07e71ee
Tx prefix hash: a3adce29e1bf073bbc1dde4b4625ad6993b8a42e1076b414d3849dcde461ad8e
Tx public key: f6c51d0ab77298432a616924c03710cd8aafb56457dc35c0a374eec5267a1429
| Timestamp: 1779473390 | Timestamp [UTC]: 2026-05-22 18:09:50 | Age [y:d:h:m:s]: 00:017:06:36:57 |
| Block: 590 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7296 | RingCT/type: yes/0 |
| Extra: 01f6c51d0ab77298432a616924c03710cd8aafb56457dc35c0a374eec5267a142902090000000293369e7d00 | ||
1 output(s) for total of 35.144867125027 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3cae6f9ea3e450e7ca3457757129a052cd30a594e287ee2b5a6325cbade0c393 | 35.144867125027 | 602 of 0 | <8a> |
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": 650,
"vin": [ {
"gen": {
"height": 590
}
}
],
"vout": [ {
"amount": 35144867125027,
"target": {
"tagged_key": {
"key": "3cae6f9ea3e450e7ca3457757129a052cd30a594e287ee2b5a6325cbade0c393",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 246, 197, 29, 10, 183, 114, 152, 67, 42, 97, 105, 36, 192, 55, 16, 205, 138, 175, 181, 100, 87, 220, 53, 192, 163, 116, 238, 197, 38, 122, 20, 41, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}