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: 1956158e69d5ea2a537cf2ae2ff9b3cd8f4645a84cedf5f7f474bc3eec1cdcb2
Tx prefix hash: b6adf885d7a917a5159371fbee8c14fee9bd5f8a8493c5469b645f842397a027
Tx public key: 5bd91ca1fe0a3af37f4671084e154bc4f4de16607331e9333028f8292cdff8d6
| Timestamp: 1779787622 | Timestamp [UTC]: 2026-05-26 09:27:02 | Age [y:d:h:m:s]: 00:018:01:35:14 |
| Block: 2187 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6558 | RingCT/type: yes/0 |
| Extra: 015bd91ca1fe0a3af37f4671084e154bc4f4de16607331e9333028f8292cdff8d602090000000126697be300 | ||
1 output(s) for total of 35.037977378456 HMNY
| stealth address | amount | amount idx | tag |
| 00: e79afb29cf7aaded69de5835c73b696d2d1b0bc9a013db67a0d5476073c71562 | 35.037977378456 | 2527 of 0 | <5c> |
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": 2247,
"vin": [ {
"gen": {
"height": 2187
}
}
],
"vout": [ {
"amount": 35037977378456,
"target": {
"tagged_key": {
"key": "e79afb29cf7aaded69de5835c73b696d2d1b0bc9a013db67a0d5476073c71562",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 91, 217, 28, 161, 254, 10, 58, 243, 127, 70, 113, 8, 78, 21, 75, 196, 244, 222, 22, 96, 115, 49, 233, 51, 48, 40, 248, 41, 44, 223, 248, 214, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}