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: 294d79719f9850ff78c6ae653fdd5370b891aa271d74ef3cc023dd73532f5291
Tx prefix hash: 151ba183780d0a6bc313c014f7b236da74f93e307f20ba0ab7644636b5ad5825
Tx public key: b288dbdb53317bfd9b945dbd05592e23f96a5246aea4a71f54be6b96ba02d7c4
| Timestamp: 1780897961 | Timestamp [UTC]: 2026-06-08 05:52:41 | Age [y:d:h:m:s]: 00:000:15:19:26 |
| Block: 7782 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 104 | RingCT/type: yes/0 |
| Extra: 01b288dbdb53317bfd9b945dbd05592e23f96a5246aea4a71f54be6b96ba02d7c40209000000014a728a4c00 | ||
1 output(s) for total of 34.666053243120 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b66149917e114828d26637af9e57558e9f9958014cf6e658ee04b4b711167dd | 34.666053243120 | 9644 of 0 | <22> |
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": 7842,
"vin": [ {
"gen": {
"height": 7782
}
}
],
"vout": [ {
"amount": 34666053243120,
"target": {
"tagged_key": {
"key": "2b66149917e114828d26637af9e57558e9f9958014cf6e658ee04b4b711167dd",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 178, 136, 219, 219, 83, 49, 123, 253, 155, 148, 93, 189, 5, 89, 46, 35, 249, 106, 82, 70, 174, 164, 167, 31, 84, 190, 107, 150, 186, 2, 215, 196, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}