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: e1a30dff83d563c61fb60b7886ceaedca2feb4320733a0a7f95875564b2e9e01
Tx prefix hash: a83f4ca4d7d88ef8dc2b56ba6722cfbce8230f1ddfeba14665e4ee456a1f55fd
Tx public key: 85f39e9e449446ca6c9f1e6f7f5091341e0237f35715bc2ba1510ce0f0f77ff9
| Timestamp: 1780984611 | Timestamp [UTC]: 2026-06-09 05:56:51 | Age [y:d:h:m:s]: 00:000:08:52:04 |
| Block: 8117 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 522 | RingCT/type: yes/0 |
| Extra: 0185f39e9e449446ca6c9f1e6f7f5091341e0237f35715bc2ba1510ce0f0f77ff9020900000001e49593ff00 | ||
1 output(s) for total of 34.643910013594 HMNY
| stealth address | amount | amount idx | tag |
| 00: f42b94f4bb5d380278f4f5620841acbf2eee022bb309582750826e5083ea9235 | 34.643910013594 | 10053 of 0 | <9f> |
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": 8177,
"vin": [ {
"gen": {
"height": 8117
}
}
],
"vout": [ {
"amount": 34643910013594,
"target": {
"tagged_key": {
"key": "f42b94f4bb5d380278f4f5620841acbf2eee022bb309582750826e5083ea9235",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 133, 243, 158, 158, 68, 148, 70, 202, 108, 159, 30, 111, 127, 80, 145, 52, 30, 2, 55, 243, 87, 21, 188, 43, 161, 81, 12, 224, 240, 247, 127, 249, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}