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: 1a976bb4a4bc871634fe947c06cc1cd84b997da7df52c016c1c24856b48fc7eb
Tx prefix hash: 304f3e83ad8f012498aea3901a8727482dde794f2a0ff56f27bb7e1d27144f0b
Tx public key: b2b916d33b2e3028151e934a0d47ef384dc77e39a4ef3cee7690c7d1c4471c47
| Timestamp: 1779797288 | Timestamp [UTC]: 2026-05-26 12:08:08 | Age [y:d:h:m:s]: 00:013:16:24:54 |
| Block: 2275 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5750 | RingCT/type: yes/0 |
| Extra: 01b2b916d33b2e3028151e934a0d47ef384dc77e39a4ef3cee7690c7d1c4471c4702090000000426697be300 | ||
1 output(s) for total of 35.032096858209 HMNY
| stealth address | amount | amount idx | tag |
| 00: 83023aa1b24b7b17df34062d8f440802bf5ca5551d4bd7177dc10a47e5c24e4a | 35.032096858209 | 2647 of 0 | <1e> |
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": 2335,
"vin": [ {
"gen": {
"height": 2275
}
}
],
"vout": [ {
"amount": 35032096858209,
"target": {
"tagged_key": {
"key": "83023aa1b24b7b17df34062d8f440802bf5ca5551d4bd7177dc10a47e5c24e4a",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 178, 185, 22, 211, 59, 46, 48, 40, 21, 30, 147, 74, 13, 71, 239, 56, 77, 199, 126, 57, 164, 239, 60, 238, 118, 144, 199, 209, 196, 71, 28, 71, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}