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: 923b3f36ede303223942d3b303c8cb5fa212c0a823ea85681822a1741e6fdd3f
Tx prefix hash: e6414b9ed6c91135d0db99b3de38bf9f583c5de61a33fde3b2c97fc2a9ac06d3
Tx public key: 448658a4c0a24342fe45c5af1e8c2d43450e5e1d123be304c9bfbb4c9cafb4f1
| Timestamp: 1779626267 | Timestamp [UTC]: 2026-05-24 12:37:47 | Age [y:d:h:m:s]: 00:015:12:58:10 |
| Block: 784 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7102 | RingCT/type: yes/0 |
| Extra: 01448658a4c0a24342fe45c5af1e8c2d43450e5e1d123be304c9bfbb4c9cafb4f1 | ||
1 output(s) for total of 35.131865016566 HMNY
| stealth address | amount | amount idx | tag |
| 00: b415b805811fb57d3d1b91fcbf5992cac6c0915771b27526ef06a843c27758e6 | 35.131865016566 | 916 of 0 | <ce> |
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": 844,
"vin": [ {
"gen": {
"height": 784
}
}
],
"vout": [ {
"amount": 35131865016566,
"target": {
"tagged_key": {
"key": "b415b805811fb57d3d1b91fcbf5992cac6c0915771b27526ef06a843c27758e6",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 68, 134, 88, 164, 192, 162, 67, 66, 254, 69, 197, 175, 30, 140, 45, 67, 69, 14, 94, 29, 18, 59, 227, 4, 201, 191, 187, 76, 156, 175, 180, 241
],
"rct_signatures": {
"type": 0
}
}