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: 14a1997dd1100d8e8a0566ef96284eff94844e810c7737b884a1f5978a5ab44d
Tx prefix hash: 7dcaaabc88c95d2daae1332bb0233a5adbbd56c2e5452e51db90f7a03c744484
Tx public key: 7045de5bba4a1774afac739f3d0fc54c9852bcd68f4194a1225b1da8b10c7b01
| Timestamp: 1779975114 | Timestamp [UTC]: 2026-05-28 13:31:54 | Age [y:d:h:m:s]: 00:011:13:17:54 |
| Block: 3877 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4022 | RingCT/type: yes/0 |
| Extra: 017045de5bba4a1774afac739f3d0fc54c9852bcd68f4194a1225b1da8b10c7b0102090000000326697be300 | ||
1 output(s) for total of 34.927836616871 HMNY
| stealth address | amount | amount idx | tag |
| 00: 426278e090d5c8fb3b93cf71424ecba43e731836231bc85eeb89c2cb39b742d1 | 34.927836616871 | 4741 of 0 | <f8> |
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": 3937,
"vin": [ {
"gen": {
"height": 3877
}
}
],
"vout": [ {
"amount": 34927836616871,
"target": {
"tagged_key": {
"key": "426278e090d5c8fb3b93cf71424ecba43e731836231bc85eeb89c2cb39b742d1",
"view_tag": "f8"
}
}
}
],
"extra": [ 1, 112, 69, 222, 91, 186, 74, 23, 116, 175, 172, 115, 159, 61, 15, 197, 76, 152, 82, 188, 214, 143, 65, 148, 161, 34, 91, 29, 168, 177, 12, 123, 1, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}