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: c151057638d1a9bf10f17d045af0b36403f187c2a8cd3434cc8607a33818b01b
Tx prefix hash: 4e237479f426c9607e77471262b54c27528b86f527af049985dfb295a0dceabe
Tx public key: 247b42d5b57e24ddf3616dd08df66053722cd9b833af9752b82d78e62d917bb4
| Timestamp: 1781000644 | Timestamp [UTC]: 2026-06-09 10:24:04 | Age [y:d:h:m:s]: 00:004:00:38:12 |
| Block: 8440 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 305 | RingCT/type: yes/0 |
| Extra: 01247b42d5b57e24ddf3616dd08df66053722cd9b833af9752b82d78e62d917bb4020900000002e49593ff00 | ||
1 output(s) for total of 34.622573367741 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9af60494b8eba697a6be58516d7a6162e6abbd40d6a1bbcb7ef8e8b607096b7a | 34.622573367741 | 10430 of 0 | <38> |
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": 8500,
"vin": [ {
"gen": {
"height": 8440
}
}
],
"vout": [ {
"amount": 34622573367741,
"target": {
"tagged_key": {
"key": "9af60494b8eba697a6be58516d7a6162e6abbd40d6a1bbcb7ef8e8b607096b7a",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 36, 123, 66, 213, 181, 126, 36, 221, 243, 97, 109, 208, 141, 246, 96, 83, 114, 44, 217, 184, 51, 175, 151, 82, 184, 45, 120, 230, 45, 145, 123, 180, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}