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: 34af9be14a6b414d2e1746fdda13ab7f4d7dee6d398a81b837ab1d8d091bb5d3
Tx prefix hash: 05a1bde073913eb67e96ef1a11608f0f916db528d3581015bfd97715c935a1f5
Tx public key: 47ad9c5d4fd4e5e8d65c4d33ae62552882d04ea9e5d65081b9851554e5f1ed8c
| Timestamp: 1779716063 | Timestamp [UTC]: 2026-05-25 13:34:23 | Age [y:d:h:m:s]: 00:014:13:06:13 |
| Block: 1648 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6248 | RingCT/type: yes/0 |
| Extra: 0147ad9c5d4fd4e5e8d65c4d33ae62552882d04ea9e5d65081b9851554e5f1ed8c020900000003ba6d17be00 | ||
1 output(s) for total of 35.074017110188 HMNY
| stealth address | amount | amount idx | tag |
| 00: 33a7084f0d744edf24de127693855d31b657fba8cf1d9811e310bf4fd2b896e7 | 35.074017110188 | 1810 of 0 | <d1> |
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": 1708,
"vin": [ {
"gen": {
"height": 1648
}
}
],
"vout": [ {
"amount": 35074017110188,
"target": {
"tagged_key": {
"key": "33a7084f0d744edf24de127693855d31b657fba8cf1d9811e310bf4fd2b896e7",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 71, 173, 156, 93, 79, 212, 229, 232, 214, 92, 77, 51, 174, 98, 85, 40, 130, 208, 78, 169, 229, 214, 80, 129, 185, 133, 21, 84, 229, 241, 237, 140, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}