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: 92609c168609553ad297957c5c886edf0db3cf05d37b90dfc4734ba3fcd036ae
Tx prefix hash: dca039e296bcfc9ae63ecfd94e93780dfe0d483da0fe8f1b487b81485a06e427
Tx public key: 93ff37d07024642e125c689638501d5ac6177427c40b7faec3d5ed7c2de76a7a
| Timestamp: 1779858972 | Timestamp [UTC]: 2026-05-27 05:16:12 | Age [y:d:h:m:s]: 00:012:20:19:45 |
| Block: 2654 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5232 | RingCT/type: yes/0 |
| Extra: 0193ff37d07024642e125c689638501d5ac6177427c40b7faec3d5ed7c2de76a7a02090000000126697be300 | ||
1 output(s) for total of 35.006781803151 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3a1aec47a03e5dc54e8d4d0d831f6af1e3db0a2a3e585b6483cb823b10031e12 | 35.006781803151 | 3128 of 0 | <31> |
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": 2714,
"vin": [ {
"gen": {
"height": 2654
}
}
],
"vout": [ {
"amount": 35006781803151,
"target": {
"tagged_key": {
"key": "3a1aec47a03e5dc54e8d4d0d831f6af1e3db0a2a3e585b6483cb823b10031e12",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 147, 255, 55, 208, 112, 36, 100, 46, 18, 92, 104, 150, 56, 80, 29, 90, 198, 23, 116, 39, 196, 11, 127, 174, 195, 213, 237, 124, 45, 231, 106, 122, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}