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: b6aa344b816dab1e89b2d1ecf342d667c78e4ab649bb3f7a175610cfb64f78f9
Tx prefix hash: 7045087d99dc58108f0dda21641ce347ef4fa3ebc88d94f62b2587881ff64cf1
Tx public key: 0d1bfc7ada062e1fcbc0c5be914dcead7a2f4047a117f4c9e7a43f47f6e9b655
| Timestamp: 1780702446 | Timestamp [UTC]: 2026-06-05 23:34:06 | Age [y:d:h:m:s]: 00:003:02:01:51 |
| Block: 6072 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1814 | RingCT/type: yes/0 |
| Extra: 010d1bfc7ada062e1fcbc0c5be914dcead7a2f4047a117f4c9e7a43f47f6e9b655020900000002e49593ff00 | ||
1 output(s) for total of 34.779303563668 HMNY
| stealth address | amount | amount idx | tag |
| 00: a26c60e5d4230e22c4bcd1b8d50af835c42e9b40eb7d901f78fdb4c4795c68ef | 34.779303563668 | 7543 of 0 | <80> |
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": 6132,
"vin": [ {
"gen": {
"height": 6072
}
}
],
"vout": [ {
"amount": 34779303563668,
"target": {
"tagged_key": {
"key": "a26c60e5d4230e22c4bcd1b8d50af835c42e9b40eb7d901f78fdb4c4795c68ef",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 13, 27, 252, 122, 218, 6, 46, 31, 203, 192, 197, 190, 145, 77, 206, 173, 122, 47, 64, 71, 161, 23, 244, 201, 231, 164, 63, 71, 246, 233, 182, 85, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}