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: df1008641230ffa1e238f5f7c22ffe4566528a689c95e32d3aa6022f064ca7de
Tx prefix hash: db6841c34e30053bca23d07b6f0a693df4a1a0397025b5963a34e910fb865d52
Tx public key: 0a7c89cc33e8a7c47925be9bfed81366cefe55ec859c601f8bbbc8d7eb84df42
| Timestamp: 1780828082 | Timestamp [UTC]: 2026-06-07 10:28:02 | Age [y:d:h:m:s]: 00:001:10:44:05 |
| Block: 7300 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 586 | RingCT/type: yes/0 |
| Extra: 010a7c89cc33e8a7c47925be9bfed81366cefe55ec859c601f8bbbc8d7eb84df42020900000001e49593ff00 | ||
1 output(s) for total of 34.697937887872 HMNY
| stealth address | amount | amount idx | tag |
| 00: ce8934125b5442b6a7a45cb030f2feab71a854a475c8a7d01affc8c04c02a478 | 34.697937887872 | 8986 of 0 | <e0> |
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": 7360,
"vin": [ {
"gen": {
"height": 7300
}
}
],
"vout": [ {
"amount": 34697937887872,
"target": {
"tagged_key": {
"key": "ce8934125b5442b6a7a45cb030f2feab71a854a475c8a7d01affc8c04c02a478",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 10, 124, 137, 204, 51, 232, 167, 196, 121, 37, 190, 155, 254, 216, 19, 102, 206, 254, 85, 236, 133, 156, 96, 31, 139, 187, 200, 215, 235, 132, 223, 66, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}