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: 6fbc2d9e9a90dd33454e7c2bc12211537141779218795bcf9e3fdd0af846f2a4
Tx prefix hash: 0171f5f729e5d1fb50be8efec82305baf75fc5753e50755574f053f52e96e4a4
Tx public key: 46b0153cd3957c5a64d888e7b40e60f97de150743959db80691f91a686cb7f93
| Timestamp: 1780999870 | Timestamp [UTC]: 2026-06-09 10:11:10 | Age [y:d:h:m:s]: 00:000:04:37:45 |
| Block: 8419 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 237 | RingCT/type: yes/0 |
| Extra: 0146b0153cd3957c5a64d888e7b40e60f97de150743959db80691f91a686cb7f93020900000001e49593ff00 | ||
1 output(s) for total of 34.634576580515 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1000a4bb7a1e751aed6ab45e2a52e891e5417ecbf13c41548ccb518da0851d40 | 34.634576580515 | 10405 of 0 | <93> |
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": 8479,
"vin": [ {
"gen": {
"height": 8419
}
}
],
"vout": [ {
"amount": 34634576580515,
"target": {
"tagged_key": {
"key": "1000a4bb7a1e751aed6ab45e2a52e891e5417ecbf13c41548ccb518da0851d40",
"view_tag": "93"
}
}
}
],
"extra": [ 1, 70, 176, 21, 60, 211, 149, 124, 90, 100, 216, 136, 231, 180, 14, 96, 249, 125, 225, 80, 116, 57, 89, 219, 128, 105, 31, 145, 166, 134, 203, 127, 147, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}