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: 1f22f13fc9e1ea5eda7eddc2c03e5ea8725b3e10064ccee0467c95aadb5d3f4c
Tx prefix hash: 79a3ac0dc669d1b2d05357114869e037dcf9292a942b31155979a12cc4e5e498
Tx public key: cd6df043a61e711598146618886854a71c2249e2c521700d73d1b4657dff11a1
| Timestamp: 1780770808 | Timestamp [UTC]: 2026-06-06 18:33:28 | Age [y:d:h:m:s]: 00:002:22:35:35 |
| Block: 6662 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2072 | RingCT/type: yes/0 |
| Extra: 01cd6df043a61e711598146618886854a71c2249e2c521700d73d1b4657dff11a1020900000001e49593ff00 | ||
1 output(s) for total of 34.740187148351 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0fd4f0d10955fa848e90028e68625fdb7cbf56b2a8cbb491a3356c849af5d17 | 34.740187148351 | 8216 of 0 | <58> |
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": 6722,
"vin": [ {
"gen": {
"height": 6662
}
}
],
"vout": [ {
"amount": 34740187148351,
"target": {
"tagged_key": {
"key": "e0fd4f0d10955fa848e90028e68625fdb7cbf56b2a8cbb491a3356c849af5d17",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 205, 109, 240, 67, 166, 30, 113, 21, 152, 20, 102, 24, 136, 104, 84, 167, 28, 34, 73, 226, 197, 33, 112, 13, 115, 209, 180, 101, 125, 255, 17, 161, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}