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: 2b77cbbf08fdca243a33702cb3e7475c9102f5df1f4abd22468f718f22cd49f9
Tx prefix hash: e3325139185ddca5dc1db87e514dbf3a70e9f0fe7abd3046087b00a15834821d
Tx public key: a7c9ddf197f1a0f39314b65c401ac3e5fa12f208c4d56e5164b270359bf5e8c0
| Timestamp: 1779953170 | Timestamp [UTC]: 2026-05-28 07:26:10 | Age [y:d:h:m:s]: 00:011:18:09:47 |
| Block: 3649 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4237 | RingCT/type: yes/0 |
| Extra: 01a7c9ddf197f1a0f39314b65c401ac3e5fa12f208c4d56e5164b270359bf5e8c002090000000726697be300 | ||
1 output(s) for total of 34.940408455114 HMNY
| stealth address | amount | amount idx | tag |
| 00: d6fb0792f088fcbe276d47dc442bf76c7cd28e48590f0928f2bd8fa53c13c480 | 34.940408455114 | 4409 of 0 | <e7> |
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": 3709,
"vin": [ {
"gen": {
"height": 3649
}
}
],
"vout": [ {
"amount": 34940408455114,
"target": {
"tagged_key": {
"key": "d6fb0792f088fcbe276d47dc442bf76c7cd28e48590f0928f2bd8fa53c13c480",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 167, 201, 221, 241, 151, 241, 160, 243, 147, 20, 182, 92, 64, 26, 195, 229, 250, 18, 242, 8, 196, 213, 110, 81, 100, 178, 112, 53, 155, 245, 232, 192, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}