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: b6f83701443b38ab579fdc74afdfa5ae1583c8613a40d0d0fccb02575d0e0fb4
Tx prefix hash: b2780562c5cdcbee4aa6fb396e27bdfa2aba68d4950fc82ddbdb91f24b023de0
Tx public key: 9be7a6b9e41029a63779241d84dd1654feec3e2b2d52324050e96108643d8cea
| Timestamp: 1780823292 | Timestamp [UTC]: 2026-06-07 09:08:12 | Age [y:d:h:m:s]: 00:001:13:16:37 |
| Block: 7214 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 672 | RingCT/type: yes/0 |
| Extra: 019be7a6b9e41029a63779241d84dd1654feec3e2b2d52324050e96108643d8cea020900000001e49593ff00 | ||
1 output(s) for total of 34.703629931664 HMNY
| stealth address | amount | amount idx | tag |
| 00: 14ffe10741640bc41d9cc0b603dbc981491b958af7191d094d16984d050bc217 | 34.703629931664 | 8884 of 0 | <86> |
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": 7274,
"vin": [ {
"gen": {
"height": 7214
}
}
],
"vout": [ {
"amount": 34703629931664,
"target": {
"tagged_key": {
"key": "14ffe10741640bc41d9cc0b603dbc981491b958af7191d094d16984d050bc217",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 155, 231, 166, 185, 228, 16, 41, 166, 55, 121, 36, 29, 132, 221, 22, 84, 254, 236, 62, 43, 45, 82, 50, 64, 80, 233, 97, 8, 100, 61, 140, 234, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}