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: 4a081701368f522919af370ada577a9f04caf45176099430bf588ffe1fcc9b00
Tx prefix hash: 7510a5102eecb9aa6e8a11a056ffe65cc31241928b248efb7f3875724ae456b3
Tx public key: 0beb97ebab7e4dbcf33b2e6b1451da883b090e34255c5b3959e2959d2563e471
| Timestamp: 1780689338 | Timestamp [UTC]: 2026-06-05 19:55:38 | Age [y:d:h:m:s]: 00:003:01:16:29 |
| Block: 5586 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2300 | RingCT/type: yes/0 |
| Extra: 010beb97ebab7e4dbcf33b2e6b1451da883b090e34255c5b3959e2959d2563e471020900000001e49593ff00 | ||
1 output(s) for total of 34.811557962524 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf8399c6e3a2c889350eda224e2dd6aad871104f7b0d7cf58b9e5bcaabae8014 | 34.811557962524 | 7031 of 0 | <fa> |
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": 5646,
"vin": [ {
"gen": {
"height": 5586
}
}
],
"vout": [ {
"amount": 34811557962524,
"target": {
"tagged_key": {
"key": "cf8399c6e3a2c889350eda224e2dd6aad871104f7b0d7cf58b9e5bcaabae8014",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 11, 235, 151, 235, 171, 126, 77, 188, 243, 59, 46, 107, 20, 81, 218, 136, 59, 9, 14, 52, 37, 92, 91, 57, 89, 226, 149, 157, 37, 99, 228, 113, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}