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: 958c49e15d7ad3e11d1bb9903eddc29ec647e587c643bd2dc9fa15a14d77d140
Tx prefix hash: 1180c062db252edb831b67c0fa12ea68fef5bcf2a02140489a5ffec29d34dbc2
Tx public key: 640f6e6de872e738276058933d7dd74a47f03cd97606f91cdafb1bf0a0439f63
| Timestamp: 1781016493 | Timestamp [UTC]: 2026-06-09 14:48:13 | Age [y:d:h:m:s]: 00:007:17:40:59 |
| Block: 8638 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 107 | RingCT/type: yes/0 |
| Extra: 01640f6e6de872e738276058933d7dd74a47f03cd97606f91cdafb1bf0a0439f63020900000003e49593ff00 | ||
1 output(s) for total of 34.609500434999 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7c7d0e555d1e4e3f6953e9b4d3e93fc47b4d11063119f5b9a6c63b83a8d64438 | 34.609500434999 | 10678 of 0 | <50> |
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": 8698,
"vin": [ {
"gen": {
"height": 8638
}
}
],
"vout": [ {
"amount": 34609500434999,
"target": {
"tagged_key": {
"key": "7c7d0e555d1e4e3f6953e9b4d3e93fc47b4d11063119f5b9a6c63b83a8d64438",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 100, 15, 110, 109, 232, 114, 231, 56, 39, 96, 88, 147, 61, 125, 215, 74, 71, 240, 60, 217, 118, 6, 249, 28, 218, 251, 27, 240, 160, 67, 159, 99, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}