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: 4519f8178cc05e8a04f67cf11871281b48dbdd33555254d73a679b11bd3566ff
Tx prefix hash: 11bd474ad94e881ebee979ee2e0ec817f83820fe583120b3a0f8f83bd2bd4a43
Tx public key: 31c8245ec4e583073fa24e49b4773f37d89163e19844dc04af47de500374bb67
| Timestamp: 1779546272 | Timestamp [UTC]: 2026-05-23 14:24:32 | Age [y:d:h:m:s]: 00:016:10:22:15 |
| Block: 693 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7193 | RingCT/type: yes/0 |
| Extra: 0131c8245ec4e583073fa24e49b4773f37d89163e19844dc04af47de500374bb67020900000006ba6d17be00 | ||
1 output(s) for total of 35.137963344644 HMNY
| stealth address | amount | amount idx | tag |
| 00: 29396d2939fcc284c4be678af5d697478ee7b7e6f732f9e6ef4f99fb8d2b155a | 35.137963344644 | 788 of 0 | <cb> |
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": 753,
"vin": [ {
"gen": {
"height": 693
}
}
],
"vout": [ {
"amount": 35137963344644,
"target": {
"tagged_key": {
"key": "29396d2939fcc284c4be678af5d697478ee7b7e6f732f9e6ef4f99fb8d2b155a",
"view_tag": "cb"
}
}
}
],
"extra": [ 1, 49, 200, 36, 94, 196, 229, 131, 7, 63, 162, 78, 73, 180, 119, 63, 55, 216, 145, 99, 225, 152, 68, 220, 4, 175, 71, 222, 80, 3, 116, 187, 103, 2, 9, 0, 0, 0, 6, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}