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: cd1b797f14d51d5fe1f42252764b0156cda2354618d76eb71038134bb42bbea5
Tx prefix hash: 4ca1ea50f6a7b6e033f5013b3528095c1305056972a7c5cc777015bbd9833d2d
Tx public key: 84e13e6c19d83fe754502431e51494655330593849fb642f4e7393a6d6d14cde
| Timestamp: 1780323178 | Timestamp [UTC]: 2026-06-01 14:12:58 | Age [y:d:h:m:s]: 00:007:10:33:49 |
| Block: 5071 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2815 | RingCT/type: yes/0 |
| Extra: 0184e13e6c19d83fe754502431e51494655330593849fb642f4e7393a6d6d14cde02090000004b26697be300 | ||
1 output(s) for total of 34.845769650611 HMNY
| stealth address | amount | amount idx | tag |
| 00: 341de5578988c1a866428c8403b47e62fa1c92dea7f2ef3d4a42d2bb352a5bf1 | 34.845769650611 | 6446 of 0 | <7e> |
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": 5131,
"vin": [ {
"gen": {
"height": 5071
}
}
],
"vout": [ {
"amount": 34845769650611,
"target": {
"tagged_key": {
"key": "341de5578988c1a866428c8403b47e62fa1c92dea7f2ef3d4a42d2bb352a5bf1",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 132, 225, 62, 108, 25, 216, 63, 231, 84, 80, 36, 49, 229, 20, 148, 101, 83, 48, 89, 56, 73, 251, 100, 47, 78, 115, 147, 166, 214, 209, 76, 222, 2, 9, 0, 0, 0, 75, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}