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: 6f06f3cb45b2b3e1676fbb87413a30520cd2fdea4b1144e8e5f078d7df9c8382
Tx prefix hash: a8510aace991ddb58567ee666df2e96eb42fc6e051a351852c2fc9d54047460f
Tx public key: a73ed640dc40bc764a6f9ea929ad38b3dd0dbbebd27ffb80ac9ec19b9f748878
| Timestamp: 1780707983 | Timestamp [UTC]: 2026-06-06 01:06:23 | Age [y:d:h:m:s]: 00:003:01:34:13 |
| Block: 6133 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1762 | RingCT/type: yes/0 |
| Extra: 01a73ed640dc40bc764a6f9ea929ad38b3dd0dbbebd27ffb80ac9ec19b9f748878020900000002e49593ff00 | ||
1 output(s) for total of 34.775257283519 HMNY
| stealth address | amount | amount idx | tag |
| 00: f5a90bbb5802efa2b3c46c4b2ccf06033210e93c25db52df7f3209e44d1acd77 | 34.775257283519 | 7608 of 0 | <49> |
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": 6193,
"vin": [ {
"gen": {
"height": 6133
}
}
],
"vout": [ {
"amount": 34775257283519,
"target": {
"tagged_key": {
"key": "f5a90bbb5802efa2b3c46c4b2ccf06033210e93c25db52df7f3209e44d1acd77",
"view_tag": "49"
}
}
}
],
"extra": [ 1, 167, 62, 214, 64, 220, 64, 188, 118, 74, 111, 158, 169, 41, 173, 56, 179, 221, 13, 187, 235, 210, 127, 251, 128, 172, 158, 193, 155, 159, 116, 136, 120, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}