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: 6bceaa5a3fb17360c7066930ff3567cc1170b5c1f66dfd5bb632971f6552f36e
Tx prefix hash: 52c3bb0c7d32e9f5c3ba42a9a22f665a7bff46b37d45cfac33f4adc75929b271
Tx public key: 49256b9dba88d312c4c26b20046ad5c2a9e4376bfdfb081ab1e4ffa82650540b
| Timestamp: 1779642101 | Timestamp [UTC]: 2026-05-24 17:01:41 | Age [y:d:h:m:s]: 00:015:10:37:09 |
| Block: 1375 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6567 | RingCT/type: yes/0 |
| Extra: 0149256b9dba88d312c4c26b20046ad5c2a9e4376bfdfb081ab1e4ffa82650540b020900000001ba6d17be00 | ||
1 output(s) for total of 35.092285140688 HMNY
| stealth address | amount | amount idx | tag |
| 00: b667017e7239ff99ef042eee6efa516ebe648436d86d3ffa609d44d832cf81a6 | 35.092285140688 | 1525 of 0 | <a0> |
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": 1435,
"vin": [ {
"gen": {
"height": 1375
}
}
],
"vout": [ {
"amount": 35092285140688,
"target": {
"tagged_key": {
"key": "b667017e7239ff99ef042eee6efa516ebe648436d86d3ffa609d44d832cf81a6",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 73, 37, 107, 157, 186, 136, 211, 18, 196, 194, 107, 32, 4, 106, 213, 194, 169, 228, 55, 107, 253, 251, 8, 26, 177, 228, 255, 168, 38, 80, 84, 11, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}