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: b6f558bf7155c6527cfd7d7772e990097dd16124195d86606b70f01852ed1883
Tx prefix hash: eba21e96da5d4a0e935dd2d5a4963b938cec334245ff8b278edccce59310ebfb
Tx public key: d8fb1cbc641e8ac6aebcb2497f150eca0a7be90cad2f93b13d91bb5f38cd6ad9
| Timestamp: 1780821812 | Timestamp [UTC]: 2026-06-07 08:43:32 | Age [y:d:h:m:s]: 00:001:16:52:25 |
| Block: 7186 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 700 | RingCT/type: yes/0 |
| Extra: 01d8fb1cbc641e8ac6aebcb2497f150eca0a7be90cad2f93b13d91bb5f38cd6ad9020900000001e49593ff00 | ||
1 output(s) for total of 34.705483356714 HMNY
| stealth address | amount | amount idx | tag |
| 00: b09a2cfadc4f79fb7c133e0bea03ff57b33ccdef424c04baa34ef00a2d1760cc | 34.705483356714 | 8852 of 0 | <94> |
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": 7246,
"vin": [ {
"gen": {
"height": 7186
}
}
],
"vout": [ {
"amount": 34705483356714,
"target": {
"tagged_key": {
"key": "b09a2cfadc4f79fb7c133e0bea03ff57b33ccdef424c04baa34ef00a2d1760cc",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 216, 251, 28, 188, 100, 30, 138, 198, 174, 188, 178, 73, 127, 21, 14, 202, 10, 123, 233, 12, 173, 47, 147, 177, 61, 145, 187, 95, 56, 205, 106, 217, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}