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: eb79ca9f261e9c9d1ce9b1b27369e54c0910e65ca9e147c60779df34fef1c9e9
Tx prefix hash: b7fbeb464bb5efb61f0b87448facadb9af69bfcd97abed80e7baf5e2fc7292c8
Tx public key: 7d88166c803183fbafbe1e54cc208227afe99c09d1c65e1b5d5a66810a241b35
| Timestamp: 1779473122 | Timestamp [UTC]: 2026-05-22 18:05:22 | Age [y:d:h:m:s]: 00:017:07:30:35 |
| Block: 587 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7299 | RingCT/type: yes/0 |
| Extra: 017d88166c803183fbafbe1e54cc208227afe99c09d1c65e1b5d5a66810a241b3502090000000293369e7d00 | ||
1 output(s) for total of 35.145068226337 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9a456dd6f1ab2ea890c9a7df1045fa3f1705729460758d1cb592f2f7ebf9e314 | 35.145068226337 | 599 of 0 | <67> |
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": 647,
"vin": [ {
"gen": {
"height": 587
}
}
],
"vout": [ {
"amount": 35145068226337,
"target": {
"tagged_key": {
"key": "9a456dd6f1ab2ea890c9a7df1045fa3f1705729460758d1cb592f2f7ebf9e314",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 125, 136, 22, 108, 128, 49, 131, 251, 175, 190, 30, 84, 204, 32, 130, 39, 175, 233, 156, 9, 209, 198, 94, 27, 93, 90, 102, 129, 10, 36, 27, 53, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}