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: b06c7de1c0ebeb25bb879cbdd1c3ee8e2b93b01e82fb101b29e7953c941e812b
Tx prefix hash: 367378f877646b777c023e2c973bc7f0f66ebc6c35f98f7a6dc196cf52a4b600
Tx public key: df7f1ec74b6d5082834bb10979ff1011c14ca8f04f21e0e98244c09e26313df5
| Timestamp: 1780690728 | Timestamp [UTC]: 2026-06-05 20:18:48 | Age [y:d:h:m:s]: 00:003:06:21:48 |
| Block: 5678 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2218 | RingCT/type: yes/0 |
| Extra: 01df7f1ec74b6d5082834bb10979ff1011c14ca8f04f21e0e98244c09e26313df5020900000001e49593ff00 | ||
1 output(s) for total of 34.805449897095 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1ab504302e79388fce20dea20f3e47fe25d6b9795fbc17f1da155531db5261c6 | 34.805449897095 | 7127 of 0 | <44> |
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": 5738,
"vin": [ {
"gen": {
"height": 5678
}
}
],
"vout": [ {
"amount": 34805449897095,
"target": {
"tagged_key": {
"key": "1ab504302e79388fce20dea20f3e47fe25d6b9795fbc17f1da155531db5261c6",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 223, 127, 30, 199, 75, 109, 80, 130, 131, 75, 177, 9, 121, 255, 16, 17, 193, 76, 168, 240, 79, 33, 224, 233, 130, 68, 192, 158, 38, 49, 61, 245, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}