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: 9a9e164383e3ea0e98328149177714da9d71753592c865445d9c50432bfa762c
Tx prefix hash: b7414e25b443d09e54f90f5f393a298f96ed298375bc33c6e7c1d22f180fa4c6
Tx public key: 46218f7863a8e8a836552ff8837d2c909af2d3a10df4f8b6aa65c5acf4b0b5ff
| Timestamp: 1780808160 | Timestamp [UTC]: 2026-06-07 04:56:00 | Age [y:d:h:m:s]: 00:001:19:50:47 |
| Block: 6981 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 905 | RingCT/type: yes/0 |
| Extra: 0146218f7863a8e8a836552ff8837d2c909af2d3a10df4f8b6aa65c5acf4b0b5ff020900000001e49593ff00 | ||
1 output(s) for total of 34.719056091526 HMNY
| stealth address | amount | amount idx | tag |
| 00: b02176912c59e969cb19cc1345302c01563d6fcb7253e49fbee1674a72c52ffd | 34.719056091526 | 8609 of 0 | <7e> |
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": 7041,
"vin": [ {
"gen": {
"height": 6981
}
}
],
"vout": [ {
"amount": 34719056091526,
"target": {
"tagged_key": {
"key": "b02176912c59e969cb19cc1345302c01563d6fcb7253e49fbee1674a72c52ffd",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 70, 33, 143, 120, 99, 168, 232, 168, 54, 85, 47, 248, 131, 125, 44, 144, 154, 242, 211, 161, 13, 244, 248, 182, 170, 101, 197, 172, 244, 176, 181, 255, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}