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: 93906f0d96f39751c65ea841675f855fca37f0ae89a0c6f4df36a17a47f11e6a
Tx prefix hash: b03bc07ca2341cbb3f6d7d138ceaecf59d708d7989e6d3eeb34a4df082d52b2a
Tx public key: e1d068a027e6285f3b6b80920c41af71d06822bc9f404f5a8b8015a4fbdfe257
| Timestamp: 1780778169 | Timestamp [UTC]: 2026-06-06 20:36:09 | Age [y:d:h:m:s]: 00:010:11:53:03 |
| Block: 6741 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2004 | RingCT/type: yes/0 |
| Extra: 01e1d068a027e6285f3b6b80920c41af71d06822bc9f404f5a8b8015a4fbdfe257020900000001e49593ff00 | ||
1 output(s) for total of 34.734952867492 HMNY
| stealth address | amount | amount idx | tag |
| 00: e90cdedb0a209bd80a02fbdacfca7630a87da1438fac29abd08850040009f6d0 | 34.734952867492 | 8317 of 0 | <95> |
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": 6801,
"vin": [ {
"gen": {
"height": 6741
}
}
],
"vout": [ {
"amount": 34734952867492,
"target": {
"tagged_key": {
"key": "e90cdedb0a209bd80a02fbdacfca7630a87da1438fac29abd08850040009f6d0",
"view_tag": "95"
}
}
}
],
"extra": [ 1, 225, 208, 104, 160, 39, 230, 40, 95, 59, 107, 128, 146, 12, 65, 175, 113, 208, 104, 34, 188, 159, 64, 79, 90, 139, 128, 21, 164, 251, 223, 226, 87, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}