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: c2847f6f2e45d8f0745c6433b1c8e076116d58e2b8a320f49065396e97017059
Tx prefix hash: 1917f100a81ea48866094d575021f0f7daa3285b32b75ff9c3434dc213459376
Tx public key: d4fcd4790200fc9427a1b62a5a4ca90356bde3883f43be4db590efb6fe60fb6b
| Timestamp: 1780692326 | Timestamp [UTC]: 2026-06-05 20:45:26 | Age [y:d:h:m:s]: 00:003:04:50:31 |
| Block: 5788 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2098 | RingCT/type: yes/0 |
| Extra: 01d4fcd4790200fc9427a1b62a5a4ca90356bde3883f43be4db590efb6fe60fb6b020900000001e49593ff00 | ||
1 output(s) for total of 34.798148182138 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9e7d86885198d96ef45cf3fe79c87eafe5a460fc4168ff21ec4fd3e80e6470c7 | 34.798148182138 | 7243 of 0 | <25> |
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": 5848,
"vin": [ {
"gen": {
"height": 5788
}
}
],
"vout": [ {
"amount": 34798148182138,
"target": {
"tagged_key": {
"key": "9e7d86885198d96ef45cf3fe79c87eafe5a460fc4168ff21ec4fd3e80e6470c7",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 212, 252, 212, 121, 2, 0, 252, 148, 39, 161, 182, 42, 90, 76, 169, 3, 86, 189, 227, 136, 63, 67, 190, 77, 181, 144, 239, 182, 254, 96, 251, 107, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}