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: 88eb9b6f4e06dd5ee24c52e0904b7718f6ebfab81e6a1ef9a40ef6704e2406f0
Tx prefix hash: 23dd492f5bb5fa9b27fe5ec336628e175543797ac67e3be5ebccbea3b0dde71a
Tx public key: f7bdf24a619017f11f05d636df7d86df1410e660268882c78e53ed93871af59e
| Timestamp: 1780770544 | Timestamp [UTC]: 2026-06-06 18:29:04 | Age [y:d:h:m:s]: 00:002:06:17:43 |
| Block: 6660 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1226 | RingCT/type: yes/0 |
| Extra: 01f7bdf24a619017f11f05d636df7d86df1410e660268882c78e53ed93871af59e020900000003e49593ff00 | ||
1 output(s) for total of 34.740319672027 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1230c5e68ec5eb7ec3d3b32675bcd0504926fac60c511b707fefdc4675a15108 | 34.740319672027 | 8212 of 0 | <c2> |
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": 6720,
"vin": [ {
"gen": {
"height": 6660
}
}
],
"vout": [ {
"amount": 34740319672027,
"target": {
"tagged_key": {
"key": "1230c5e68ec5eb7ec3d3b32675bcd0504926fac60c511b707fefdc4675a15108",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 247, 189, 242, 74, 97, 144, 23, 241, 31, 5, 214, 54, 223, 125, 134, 223, 20, 16, 230, 96, 38, 136, 130, 199, 142, 83, 237, 147, 135, 26, 245, 158, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}