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: ed209f2087a30475d9c2c04f4091ac9e1e463fde44b9adefee40179c6760a8c3
Tx prefix hash: 40ae311bf4c7cd8ea5377e0cf613dd0e663ea193c362c79fdae1416ff4fc1b16
Tx public key: 1f6e53fee80e5f7a189d8979bb109fa63f48700b7369c394cbd8af5f78ad3920
| Timestamp: 1780042538 | Timestamp [UTC]: 2026-05-29 08:15:38 | Age [y:d:h:m:s]: 00:010:16:31:09 |
| Block: 4305 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3581 | RingCT/type: yes/0 |
| Extra: 011f6e53fee80e5f7a189d8979bb109fa63f48700b7369c394cbd8af5f78ad392002090000000126697be300 | ||
1 output(s) for total of 34.896717590170 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18ffdb01a0ec063da83f24c477e379cc21332764991f4c8afab817e2a366df1c | 34.896717590170 | 5379 of 0 | <fe> |
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": 4365,
"vin": [ {
"gen": {
"height": 4305
}
}
],
"vout": [ {
"amount": 34896717590170,
"target": {
"tagged_key": {
"key": "18ffdb01a0ec063da83f24c477e379cc21332764991f4c8afab817e2a366df1c",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 31, 110, 83, 254, 232, 14, 95, 122, 24, 157, 137, 121, 187, 16, 159, 166, 63, 72, 112, 11, 115, 105, 195, 148, 203, 216, 175, 95, 120, 173, 57, 32, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}