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: 48dea9de853581f185ae694f854c70fc742fa179267852af05bd47c42134323f
Tx prefix hash: 9e4a7e0f8eacdfcae220aaba3ee18ef69ee044b7e448971d8db130dfae68ee2f
Tx public key: b248e2ec388af14c0e91d7d8d912fad168c963543106c15fd86ad2f4893731b4
| Timestamp: 1780999727 | Timestamp [UTC]: 2026-06-09 10:08:47 | Age [y:d:h:m:s]: 00:000:04:40:08 |
| Block: 8418 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 224 | RingCT/type: yes/0 |
| Extra: 01b248e2ec388af14c0e91d7d8d912fad168c963543106c15fd86ad2f4893731b4020900000004e49593ff00 | ||
1 output(s) for total of 34.624026220604 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a420345ddf960e53051ffac00c810d2e7a8fe9cf5b3c842eba91dfdf1a83ad8 | 34.624026220604 | 10404 of 0 | <92> |
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": 8478,
"vin": [ {
"gen": {
"height": 8418
}
}
],
"vout": [ {
"amount": 34624026220604,
"target": {
"tagged_key": {
"key": "5a420345ddf960e53051ffac00c810d2e7a8fe9cf5b3c842eba91dfdf1a83ad8",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 178, 72, 226, 236, 56, 138, 241, 76, 14, 145, 215, 216, 217, 18, 250, 209, 104, 201, 99, 84, 49, 6, 193, 95, 216, 106, 210, 244, 137, 55, 49, 180, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}