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: 7849924d61a607b9b1c174e22b0bea3d3f95c2504b450c4a57d401ec54da947a
Tx prefix hash: 0da88eece30849e49df1988d85f8205c1e135e40bdb30b01d0280b2efc566458
Tx public key: ab3706622c73718f659543cc99c1f6a87e62333a93c4f645a753a8295607e61f
| Timestamp: 1779807174 | Timestamp [UTC]: 2026-05-26 14:52:54 | Age [y:d:h:m:s]: 00:013:12:58:04 |
| Block: 2362 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5604 | RingCT/type: yes/0 |
| Extra: 01ab3706622c73718f659543cc99c1f6a87e62333a93c4f645a753a8295607e61f02090000000526697be300 | ||
1 output(s) for total of 35.026284132240 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe0717e64cbba8d98c57a04ae5b42b6a3778286d3f54fd0f4c47a0432c38378c | 35.026284132240 | 2768 of 0 | <5e> |
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": 2422,
"vin": [ {
"gen": {
"height": 2362
}
}
],
"vout": [ {
"amount": 35026284132240,
"target": {
"tagged_key": {
"key": "fe0717e64cbba8d98c57a04ae5b42b6a3778286d3f54fd0f4c47a0432c38378c",
"view_tag": "5e"
}
}
}
],
"extra": [ 1, 171, 55, 6, 98, 44, 115, 113, 143, 101, 149, 67, 204, 153, 193, 246, 168, 126, 98, 51, 58, 147, 196, 246, 69, 167, 83, 168, 41, 86, 7, 230, 31, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}