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: 78f70e24d8abf16155d1b52410fb4d7d82f283861c76f22e78cf3934d9103170
Tx prefix hash: 4d071e0e5603eff7761f3bb181ee6ab510df5c53607110f6e07a31455a4c8509
Tx public key: a49d32af4dd6fe6a1b9da725b8f34e3cb8297dc44565b000db62509e5cd0a6da
| Timestamp: 1781023193 | Timestamp [UTC]: 2026-06-09 16:39:53 | Age [y:d:h:m:s]: 00:006:03:47:05 |
| Block: 8719 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 26 | RingCT/type: yes/0 |
| Extra: 01a49d32af4dd6fe6a1b9da725b8f34e3cb8297dc44565b000db62509e5cd0a6da020900000003e49593ff00 | ||
1 output(s) for total of 34.604153839873 HMNY
| stealth address | amount | amount idx | tag |
| 00: d1ac7712c65fd5905b2339d58b4cbb16ef13f97b3e4c557321a65e8f4bb58161 | 34.604153839873 | 10783 of 0 | <cf> |
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": 8779,
"vin": [ {
"gen": {
"height": 8719
}
}
],
"vout": [ {
"amount": 34604153839873,
"target": {
"tagged_key": {
"key": "d1ac7712c65fd5905b2339d58b4cbb16ef13f97b3e4c557321a65e8f4bb58161",
"view_tag": "cf"
}
}
}
],
"extra": [ 1, 164, 157, 50, 175, 77, 214, 254, 106, 27, 157, 167, 37, 184, 243, 78, 60, 184, 41, 125, 196, 69, 101, 176, 0, 219, 98, 80, 158, 92, 208, 166, 218, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}