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: 4d0a327f436690315c56c17c0f66034ca15610160c2f3eda5800344c7ee3a775
Tx prefix hash: 97d8c143087b06ece23b2f0705f654a51a5f0c70f8ed7ca0f7e487984b659ce5
Tx public key: f61402d0c5657f5972f95f2bb01efa323c51fc045494079a2b63ab6cfa42da70
| Timestamp: 1780706677 | Timestamp [UTC]: 2026-06-06 00:44:37 | Age [y:d:h:m:s]: 00:003:00:51:20 |
| Block: 6117 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1769 | RingCT/type: yes/0 |
| Extra: 01f61402d0c5657f5972f95f2bb01efa323c51fc045494079a2b63ab6cfa42da70020900000002e49593ff00 | ||
1 output(s) for total of 34.776318557356 HMNY
| stealth address | amount | amount idx | tag |
| 00: 76e18c123c625f9071c3753ca9095465549ca4f6adab5b5f14e88396f64685bd | 34.776318557356 | 7590 of 0 | <73> |
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": 6177,
"vin": [ {
"gen": {
"height": 6117
}
}
],
"vout": [ {
"amount": 34776318557356,
"target": {
"tagged_key": {
"key": "76e18c123c625f9071c3753ca9095465549ca4f6adab5b5f14e88396f64685bd",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 246, 20, 2, 208, 197, 101, 127, 89, 114, 249, 95, 43, 176, 30, 250, 50, 60, 81, 252, 4, 84, 148, 7, 154, 43, 99, 171, 108, 250, 66, 218, 112, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}