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: 5a1decfe5db854e07c478d1f8fdbcfc18da4f843521e78d02d32c5089f4f0351
Tx prefix hash: 2b7d7239df81440a46f3258f95d9918b8d93ca4ed9eb0440facdaa15387de064
Tx public key: 0567cb1fbd4b5f402bb27f6db360d71d6b15de80f120b17dba060abf20e910af
| Timestamp: 1780108789 | Timestamp [UTC]: 2026-05-30 02:39:49 | Age [y:d:h:m:s]: 00:010:00:00:47 |
| Block: 4845 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3052 | RingCT/type: yes/0 |
| Extra: 010567cb1fbd4b5f402bb27f6db360d71d6b15de80f120b17dba060abf20e910af02090000000d26697be300 | ||
1 output(s) for total of 34.863414347842 HMNY
| stealth address | amount | amount idx | tag |
| 00: c791b959dbb0012a671a2e2741e92c53f66805757a3c5bb6ecc1778f9e20783b | 34.863414347842 | 6111 of 0 | <83> |
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": 4905,
"vin": [ {
"gen": {
"height": 4845
}
}
],
"vout": [ {
"amount": 34863414347842,
"target": {
"tagged_key": {
"key": "c791b959dbb0012a671a2e2741e92c53f66805757a3c5bb6ecc1778f9e20783b",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 5, 103, 203, 31, 189, 75, 95, 64, 43, 178, 127, 109, 179, 96, 215, 29, 107, 21, 222, 128, 241, 32, 177, 125, 186, 6, 10, 191, 32, 233, 16, 175, 2, 9, 0, 0, 0, 13, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}