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: 027f37d2adb24dc3c2b993b625c773d42d4a9d5015a0f4b331ce3b00c7509f50
Tx prefix hash: 6e086341d7535168f0f02782d9319c0aff1b086d5553741c93b16466af69fa7b
Tx public key: a32ca7d22e8423fc09b1e0dbe7650f7fd4f413f72977fa3a5a70b796dc07cec0
| Timestamp: 1780814965 | Timestamp [UTC]: 2026-06-07 06:49:25 | Age [y:d:h:m:s]: 00:001:17:57:22 |
| Block: 7047 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 839 | RingCT/type: yes/0 |
| Extra: 01a32ca7d22e8423fc09b1e0dbe7650f7fd4f413f72977fa3a5a70b796dc07cec0020900000001e49593ff00 | ||
1 output(s) for total of 34.724507753729 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3758134d921c8ea3faa6b7d89f38efef758ddb48fc02b3e0bdb91b9695925c4 | 34.724507753729 | 8689 of 0 | <d8> |
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": 7107,
"vin": [ {
"gen": {
"height": 7047
}
}
],
"vout": [ {
"amount": 34724507753729,
"target": {
"tagged_key": {
"key": "b3758134d921c8ea3faa6b7d89f38efef758ddb48fc02b3e0bdb91b9695925c4",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 163, 44, 167, 210, 46, 132, 35, 252, 9, 177, 224, 219, 231, 101, 15, 127, 212, 244, 19, 247, 41, 119, 250, 58, 90, 112, 183, 150, 220, 7, 206, 192, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}