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: a8460862deebbc6e796a1b15cae21d715222cc184e22c00e31475228787d5b20
Tx prefix hash: a107abd1cd476df06a3df2fbf4c93c37bc90f40cccedf8803af3b2bd03c251cc
Tx public key: dc9fa0a64424d30daa38ec9943103df30234b10c883c3c06eab2a334feddc243
| Timestamp: 1781018726 | Timestamp [UTC]: 2026-06-09 15:25:26 | Age [y:d:h:m:s]: 00:006:03:56:43 |
| Block: 8664 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 81 | RingCT/type: yes/0 |
| Extra: 01dc9fa0a64424d30daa38ec9943103df30234b10c883c3c06eab2a334feddc243020900000001e49593ff00 | ||
1 output(s) for total of 34.607784153952 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8328149ed3ebab2ddbe64786876cd776d4fd9771e4d887895c983fbb17c0f2ac | 34.607784153952 | 10712 of 0 | <b6> |
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": 8724,
"vin": [ {
"gen": {
"height": 8664
}
}
],
"vout": [ {
"amount": 34607784153952,
"target": {
"tagged_key": {
"key": "8328149ed3ebab2ddbe64786876cd776d4fd9771e4d887895c983fbb17c0f2ac",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 220, 159, 160, 166, 68, 36, 211, 13, 170, 56, 236, 153, 67, 16, 61, 243, 2, 52, 177, 12, 136, 60, 60, 6, 234, 178, 163, 52, 254, 221, 194, 67, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}