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: ea3530a753b02034d19d72ba5723b98810730a791f122cffcea3c30f91689528
Tx prefix hash: 38d877e4bbfc5b7972da2dd4f120b0d39bd5356d6724dc7a9a3c13f7cfe04284
Tx public key: d01f138d6707c849d13733b9761a49b2c42e96394564a3c20db8367d6ef4b6ab
| Timestamp: 1780781065 | Timestamp [UTC]: 2026-06-06 21:24:25 | Age [y:d:h:m:s]: 00:002:01:54:28 |
| Block: 6764 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1122 | RingCT/type: yes/0 |
| Extra: 01d01f138d6707c849d13733b9761a49b2c42e96394564a3c20db8367d6ef4b6ab020900000004e49593ff00 | ||
1 output(s) for total of 34.733429111170 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4f0eb9e2892e499948e8e75775b34f606d9fc02474d60f0f650b07e39c26c4f0 | 34.733429111170 | 8350 of 0 | <a3> |
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": 6824,
"vin": [ {
"gen": {
"height": 6764
}
}
],
"vout": [ {
"amount": 34733429111170,
"target": {
"tagged_key": {
"key": "4f0eb9e2892e499948e8e75775b34f606d9fc02474d60f0f650b07e39c26c4f0",
"view_tag": "a3"
}
}
}
],
"extra": [ 1, 208, 31, 19, 141, 103, 7, 200, 73, 209, 55, 51, 185, 118, 26, 73, 178, 196, 46, 150, 57, 69, 100, 163, 194, 13, 184, 54, 125, 110, 244, 182, 171, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}