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: dd5b7e288c86cf5f81c45ee6685d707c3c2ae1380930ad46989d4a69511dda4d
Tx prefix hash: 787c9d860d454c22209e331bf04d1d1790d8fabea8c33cd4e77dbf5180411a36
Tx public key: 6afd9f1085394ddb06b0026216b3ba3859692731650eb9aecc7345e2514d9f19
| Timestamp: 1779460799 | Timestamp [UTC]: 2026-05-22 14:39:59 | Age [y:d:h:m:s]: 00:017:10:55:58 |
| Block: 435 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7451 | RingCT/type: yes/0 |
| Extra: 016afd9f1085394ddb06b0026216b3ba3859692731650eb9aecc7345e2514d9f1902090000000793369e7d00 | ||
1 output(s) for total of 35.155258865675 HMNY
| stealth address | amount | amount idx | tag |
| 00: 532abe7d56752ac356f5762eb1c61c5db7e0adcf52d4522dc8e4b381153f6c7c | 35.155258865675 | 439 of 0 | <b4> |
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": 495,
"vin": [ {
"gen": {
"height": 435
}
}
],
"vout": [ {
"amount": 35155258865675,
"target": {
"tagged_key": {
"key": "532abe7d56752ac356f5762eb1c61c5db7e0adcf52d4522dc8e4b381153f6c7c",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 106, 253, 159, 16, 133, 57, 77, 219, 6, 176, 2, 98, 22, 179, 186, 56, 89, 105, 39, 49, 101, 14, 185, 174, 204, 115, 69, 226, 81, 77, 159, 25, 2, 9, 0, 0, 0, 7, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}