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: 6da4ecb61a55f1b8e6417665628c776f9ca428510c83189a81477e9d6016fa54
Tx prefix hash: 6f303600f43ea0e4f904029d4dbe1cbad33995e5e28f9d181e1d1ac2822c4bc4
Tx public key: 03568f2da72e972cb57f2cba3e1c6720cc8639973a0740d39171a53b333bbc45
| Timestamp: 1780726047 | Timestamp [UTC]: 2026-06-06 06:07:27 | Age [y:d:h:m:s]: 00:002:18:39:20 |
| Block: 6272 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1614 | RingCT/type: yes/0 |
| Extra: 0103568f2da72e972cb57f2cba3e1c6720cc8639973a0740d39171a53b333bbc45020900000001e49593ff00 | ||
1 output(s) for total of 34.766038829805 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f86a34961a1138cba4d14300283a37cc2bb5ae4d6403db7166d2c06db8eb54e | 34.766038829805 | 7755 of 0 | <57> |
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": 6332,
"vin": [ {
"gen": {
"height": 6272
}
}
],
"vout": [ {
"amount": 34766038829805,
"target": {
"tagged_key": {
"key": "2f86a34961a1138cba4d14300283a37cc2bb5ae4d6403db7166d2c06db8eb54e",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 3, 86, 143, 45, 167, 46, 151, 44, 181, 127, 44, 186, 62, 28, 103, 32, 204, 134, 57, 151, 58, 7, 64, 211, 145, 113, 165, 59, 51, 59, 188, 69, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}