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: f149baab57d0acb1c870e51f9b5fb4dfada8b9b7f72b856f08e823de7cede62d
Tx prefix hash: cf64c36f682a09d002e4c202c582b10f873c6e3cc16429023e9612b15fe67d65
Tx public key: d6497445701bf7d0c9e049d5c1874a8b90ae7c7da9cb24290cd44e987f9dfe3f
| Timestamp: 1779474630 | Timestamp [UTC]: 2026-05-22 18:30:30 | Age [y:d:h:m:s]: 00:017:04:48:23 |
| Block: 599 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7287 | RingCT/type: yes/0 |
| Extra: 01d6497445701bf7d0c9e049d5c1874a8b90ae7c7da9cb24290cd44e987f9dfe3f02090000000293369e7d00 | ||
1 output(s) for total of 35.144263828002 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c9bb8c513eafda3cdd706ee4a5794143ef7f895e3ead98e4111509591d0419a | 35.144263828002 | 613 of 0 | <ba> |
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": 659,
"vin": [ {
"gen": {
"height": 599
}
}
],
"vout": [ {
"amount": 35144263828002,
"target": {
"tagged_key": {
"key": "8c9bb8c513eafda3cdd706ee4a5794143ef7f895e3ead98e4111509591d0419a",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 214, 73, 116, 69, 112, 27, 247, 208, 201, 224, 73, 213, 193, 135, 74, 139, 144, 174, 124, 125, 169, 203, 36, 41, 12, 212, 78, 152, 127, 157, 254, 63, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}