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: e5e6463d2f74574f716f4ebb5990c2ee1fef85decb049d3dd31ce9f3457a442f
Tx prefix hash: 8e79f2a418357e5ac537739019d55dda7b651b9b4262c454833cf98e4148c0a6
Tx public key: 5d36036d8b74bb7043a551d2f81157cb5c17c6f7aff68a917a781177cd0894b8
| Timestamp: 1780025104 | Timestamp [UTC]: 2026-05-29 03:25:04 | Age [y:d:h:m:s]: 00:010:22:10:53 |
| Block: 4165 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3721 | RingCT/type: yes/0 |
| Extra: 015d36036d8b74bb7043a551d2f81157cb5c17c6f7aff68a917a781177cd0894b802090000000426697be300 | ||
1 output(s) for total of 34.933459672237 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5430b9be701ca8d1101ad477543e16262d0b3b12a5368180888d1cbb1f66c09d | 34.933459672237 | 5196 of 0 | <82> |
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": 4225,
"vin": [ {
"gen": {
"height": 4165
}
}
],
"vout": [ {
"amount": 34933459672237,
"target": {
"tagged_key": {
"key": "5430b9be701ca8d1101ad477543e16262d0b3b12a5368180888d1cbb1f66c09d",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 93, 54, 3, 109, 139, 116, 187, 112, 67, 165, 81, 210, 248, 17, 87, 203, 92, 23, 198, 247, 175, 246, 138, 145, 122, 120, 17, 119, 205, 8, 148, 184, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}