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: 4d6cef36909cb6e728b7d3b0f6e36e7873161ee524f92459f9e7649e130a3c1e
Tx prefix hash: d6d9a77ce591367aa851d5b2c269ace6a38789e030bec8e33fedbc21df915e6b
Tx public key: 4d609fee29619b9e276fd74b3e33500747622182bf96a4549045339ed8ffd695
| Timestamp: 1780694151 | Timestamp [UTC]: 2026-06-05 21:15:51 | Age [y:d:h:m:s]: 00:003:04:20:06 |
| Block: 5917 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1969 | RingCT/type: yes/0 |
| Extra: 014d609fee29619b9e276fd74b3e33500747622182bf96a4549045339ed8ffd695020900000001e49593ff00 | ||
1 output(s) for total of 34.789587213375 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0617c7df09feb1d78d0185845554dbdd7f7a4c1e20176b8386bc16df31e828ec | 34.789587213375 | 7378 of 0 | <2d> |
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": 5977,
"vin": [ {
"gen": {
"height": 5917
}
}
],
"vout": [ {
"amount": 34789587213375,
"target": {
"tagged_key": {
"key": "0617c7df09feb1d78d0185845554dbdd7f7a4c1e20176b8386bc16df31e828ec",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 77, 96, 159, 238, 41, 97, 155, 158, 39, 111, 215, 75, 62, 51, 80, 7, 71, 98, 33, 130, 191, 150, 164, 84, 144, 69, 51, 158, 216, 255, 214, 149, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}