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: 2a9961c88e9cb7349d0d37337b2f668a34acaeb0110d19f0510cbb43e0743b6a
Tx prefix hash: 5989144043a7f7b4070a9bba64a0423e68833e2efd4073213d9f84ffe10de1f4
Tx public key: 7b53eadffad7c1b60b00e829a29a76db62f5f7246f48663c052e3e664ec173dd
| Timestamp: 1779865450 | Timestamp [UTC]: 2026-05-27 07:04:10 | Age [y:d:h:m:s]: 00:012:20:34:40 |
| Block: 2736 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5210 | RingCT/type: yes/0 |
| Extra: 017b53eadffad7c1b60b00e829a29a76db62f5f7246f48663c052e3e664ec173dd02090000000126697be300 | ||
1 output(s) for total of 35.001307074805 HMNY
| stealth address | amount | amount idx | tag |
| 00: 75db96cbaa073e49b8cee538ef24f608863bfbc14b98126fb9f5e4997f72f37b | 35.001307074805 | 3232 of 0 | <b1> |
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": 2796,
"vin": [ {
"gen": {
"height": 2736
}
}
],
"vout": [ {
"amount": 35001307074805,
"target": {
"tagged_key": {
"key": "75db96cbaa073e49b8cee538ef24f608863bfbc14b98126fb9f5e4997f72f37b",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 123, 83, 234, 223, 250, 215, 193, 182, 11, 0, 232, 41, 162, 154, 118, 219, 98, 245, 247, 36, 111, 72, 102, 60, 5, 46, 62, 102, 78, 193, 115, 221, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}