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: 884d8b2b134deaf3b5d80917e5dbeeca2e841a1a5c24de4ca7f70b93e5cc6cc3
Tx prefix hash: 266c837f7bb5f7a3d273c17c3a90afd286940e4f23dcb86e56b2f528ecf5b9f0
Tx public key: 4c4460c387084cf4c869badc6606517970ef3a6e6197189f67a398ecc7936370
| Timestamp: 1780686290 | Timestamp [UTC]: 2026-06-05 19:04:50 | Age [y:d:h:m:s]: 00:007:15:57:26 |
| Block: 5417 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3328 | RingCT/type: yes/0 |
| Extra: 014c4460c387084cf4c869badc6606517970ef3a6e6197189f67a398ecc7936370020900000001e49593ff00 | ||
1 output(s) for total of 34.822781006353 HMNY
| stealth address | amount | amount idx | tag |
| 00: 266c883fdf52a87e52de23cfe7ce3fa58b2699681715a8d1170d0f7a5b6c305e | 34.822781006353 | 6854 of 0 | <dc> |
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": 5477,
"vin": [ {
"gen": {
"height": 5417
}
}
],
"vout": [ {
"amount": 34822781006353,
"target": {
"tagged_key": {
"key": "266c883fdf52a87e52de23cfe7ce3fa58b2699681715a8d1170d0f7a5b6c305e",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 76, 68, 96, 195, 135, 8, 76, 244, 200, 105, 186, 220, 102, 6, 81, 121, 112, 239, 58, 110, 97, 151, 24, 159, 103, 163, 152, 236, 199, 147, 99, 112, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}