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: b3c257a206b486f91d851181d9b747cac10dde453c1458bcf7473d16c896ca55
Tx prefix hash: 7ee0c97e14e38af252a99b36aaf923e9faf3494ade920c37cf9b3379b4e527a8
Tx public key: 58eb574706d05d64ad53053eee3ca447d30253c0050844453a165fd2a0e04ac6
| Timestamp: 1779779156 | Timestamp [UTC]: 2026-05-26 07:05:56 | Age [y:d:h:m:s]: 00:013:19:43:52 |
| Block: 2086 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5834 | RingCT/type: yes/0 |
| Extra: 0158eb574706d05d64ad53053eee3ca447d30253c0050844453a165fd2a0e04ac602090000000226697be300 | ||
1 output(s) for total of 35.047337828547 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64c885828d31996eb19c14acb9ee4a3e876088c8beeb51154bcac34dc70ecbfb | 35.047337828547 | 2396 of 0 | <60> |
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": 2146,
"vin": [ {
"gen": {
"height": 2086
}
}
],
"vout": [ {
"amount": 35047337828547,
"target": {
"tagged_key": {
"key": "64c885828d31996eb19c14acb9ee4a3e876088c8beeb51154bcac34dc70ecbfb",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 88, 235, 87, 71, 6, 208, 93, 100, 173, 83, 5, 62, 238, 60, 164, 71, 211, 2, 83, 192, 5, 8, 68, 69, 58, 22, 95, 210, 160, 224, 74, 198, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}