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: 7ea69dad352fc8144ff498994bbac1e3bd63763cf245c56a3855437fa48a4f2b
Tx prefix hash: a83636dc639066d1e4ee49128b2e2569d0dce3d690ec527617ba5b6fc6728554
Tx public key: 773f2a13a8f493f32647b65d5441be1ff1854b41921e8804534ac4b4deed3e52
| Timestamp: 1779634357 | Timestamp [UTC]: 2026-05-24 14:52:37 | Age [y:d:h:m:s]: 00:015:12:46:13 |
| Block: 1034 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6911 | RingCT/type: yes/0 |
| Extra: 01773f2a13a8f493f32647b65d5441be1ff1854b41921e8804534ac4b4deed3e52020900000002ba6d17be00 | ||
1 output(s) for total of 35.115116815316 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8159ace80a3899699edcc65f1a3bc66a8d8cc6223bfc81eed633b90d967a9480 | 35.115116815316 | 1172 of 0 | <47> |
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": 1094,
"vin": [ {
"gen": {
"height": 1034
}
}
],
"vout": [ {
"amount": 35115116815316,
"target": {
"tagged_key": {
"key": "8159ace80a3899699edcc65f1a3bc66a8d8cc6223bfc81eed633b90d967a9480",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 119, 63, 42, 19, 168, 244, 147, 243, 38, 71, 182, 93, 84, 65, 190, 31, 241, 133, 75, 65, 146, 30, 136, 4, 83, 74, 196, 180, 222, 237, 62, 82, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}